-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Severity 3 - Minor
-
0
-
Issue Summary
Having at least 2 release versions, in two JSM projects, and configuring then to display on a Jira Road Map gadget. It throws the following error when accessing the version from the gadget:
"Permission Violation
It seems that you have tried to perform an operation which you are not permitted to perform.
If you think this message is wrong, null."
The URL that returns the error is https://<instance>.atlassian.net/browse/<projectkey>/fixforversion/<versionID>
Steps to Reproduce
- Have 2 JSM projects
- Have at least 1 version on each JSM project with a specified Release date
- Create a Jira Road Map gadget and make sure both versions from the two different projects are displayed
- Try to access both versions through the gadget
Expected Results
You're redirected to the URL https://<instance>.atlassian.net/browse/<projectkey>/fixforversion/<versionID> for both cases and is able to view both versions' information.
Actual Results
You're redirected to URL https://<instance>.atlassian.net/browse/<projectkey>/fixforversion/<versionID>, and one version is displayed as expected but the other will return the Permission Violation error.
If you have more than two JSM projects displaying information on this gadget, then it shall only work for one project and it will fail for the others.
Workaround
Currently, there is no known workaround for this behavior.
However, it's possible to see the information of the version by accessing the project > Project settings > Versions, then going on the gadget and clicking on the version there.
With this, the project you just accessed will work on the gadget, but the others will fail.
You can do that to each project, just to view the information if required.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team