Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Transferring Issues across Boards with Smart Commits

BG June 12, 2019

Guys, any guidance would be appreciated. I contacted Jira support and they basically said I'm SOL. I have over 2000 issues being affected by this.

I had the following Classic Jira board:

Original Board with the key COMPANY-XXXX (So Jira tasks are created as COMPANY-1, COMPANY-1234, etc)

I then migrated, in no particular order, my issues from my Original Board over to a Next Gen board. My next gen board has the key COMP-XXXX.

 

My issues on my new board is tracing commits from totally different issues.

 

For example, if I moved the following issues over to the new board like so:

COMPANY-1 => COMP-5

COMPANY-5 => COMP-234

 

COMP-5 is now showing my commit history from COMPANY-5 instead of COMPANY-1. And COMP-234 is showing my issues from COMPANY-234, instead of COMPANY-5.

 

Why would this feature not take into account my keys and just the issue number? Has anyone had this issue before? Does anyone have any reocmmendations to fix, or completely clear these commits.

This is a huge bug that has taken away over 6 months of data from our team's commit history and if I knew this would be an issue I would have never switched.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events