How do I fix the name change of swimlane after upgrade for other issues?
We recently upgraded our Jira Data Center from 7.8 to 8.2 a few weeks ago and everything went well. A few support tickets came across displaying a weird header on the swimlane.
So, on a scrum board, we have our swimlanes separated by stories. The bucket that regards other issues that are not stories or associated to a story (Like a sub-task) now has a swimlane of gh.rapid.swimlane.parentchild.default.name
I was wondering if anyone has ever experienced this and if so, what was done to fix it?
I have checked the system add-ons, I have changed the board configuration and changed it back, I have performed a re-index. I am not sure what else can be done because everything else after the upgrade is working great.
1 answer
1 accepted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.