I have the exact same issue as the one reported here: JRA-47564. Status for this issue is Resolved, but I can reproduce on my own Server instance (JIRA Software 7.2.7, Chrome 56.0.2924.87 (64-bit)).
In which JIRA version is the above issue fixed ?
The "Resolved" status on https://jira.atlassian.com/browse/JRA-47564 doesn't necessarily mean it was fixed (or even that Atlassian found it to be a bug). It just means that the issue wasn't progressed in https://jira.atlassian.com.
The "Resolution" for the issue shows "Support Request" which means (as per the comments on there) that Atlassian asked the reporter to raise a support request so that they could help resolve the issue for them on a non-public forum.
It's probably worth you doing the same via: https://support.atlassian.com/servicedesk/customer/portal/20 (which is the ServiceDesk for JIRA Software issues). Atlassian are usually very helpful in working through and resolving issues. They may raise a bug for you in https://jira.atlassian.com if it is a wider problem.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs