Hello,
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 ?
Thanks.
--
Eric
Hi Eric,
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.
Sam
Just to add to this, for bugs that have been fixed and released, Atlassian normally set Resolution to 'Fixed' and show which versions fix the issue in the Fix Versions field. For example, like:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.