-
Bug
-
Resolution: Fixed
-
High
-
8
-
Minor
-
Issue Summary
Colours of epic links are not displayed accurately on the board and backlog of company-managed software projects when migrating issues via Jira Cloud Migration Assistant. All of them are set to grey.
if you pick one issue it will show the epic link field and the color properly assigned to it in issue view. You can also edit the epic link and it shows the proper color.
This is happening for both Scrum and Kanban bords.
It also looks like the color for the Fix Versions are not coming across properly and are also gray.
See screenshots:
This is reproducible on Data Center: not sure
Steps to Reproduce
- Migrates a child issue and its parent epic via Jira Cloud Migration Assistant
Expected Results
Epic link colours display accurately on board and backlog.
Actual Results
Epic link colours are all grey.
Root cause & Background information
The root cause is that we’re moving from consuming Epic Color to consuming Issue Color in Jira as part of the Epic related fields deprecation.
Basically, Epic Color should be kept in sync with the Issue Color field value. However, we’ve discovered that if the user migrates an issue via Jira Cloud Migration Assistant this syncing does not occur and causes Epics that are imported in this way to not have an Issue Color value. The frontend in the meantime in our rollout, has moved to consuming the Issue Color value. Grey is the default value, which is why this is showing grey in the backlog.
Workaround
Please open a support ticket with Atlassian and refer them to this bug.
Internal staff, please refer to the first comment.
The cause in the case of migrations was fixed, and the data was resynced so that customers that have migrated since this bug began will have their data properly migrated. Closing as fixed.
Note: this can still appear if the Jira instance being migrated from server to cloud does not have Epic Color values for issues. The logic currently used only creates corresponding Issue Color values (which is now what is consumed in the board/backlog/issue view) based on the existing Epic Color value. If there is no Epic Color value to begin with, nothing is done.