Hi everyone,
We are experiencing a little issue, which I would like to receive your feedback on possible solutions, as the behavior, according to atlassian, is what it's expected.
Scenario:
1) issue X in Project A within sprint XPTO
2) we move issue X from Proj A to Proj B
3) issue X is now available in PRJ B, but also within sprint XPTO*
sprint XPTO* is duplicated in Proj B, from Proj A, as seems to be a mirror/pointer to the original sprint.
For instance, if we delete in Proj B the sprint XPTO", it will delete also sprint XPTO in Proj A.
Do you have any ideas to workaround this?
we have script runner installed. would it be possible for instance to modify the "Move" function and force to always reset/set empty the field "sprint" ?
Thank you
Hello,
The behaviour is correct. Sprints do not belong to boards. If an issue is included in a sprint, then this sprint will be visible on all boards, which show the issue. You should edit the sprint field for your issue and remove the sprint from the XPTO sprint. In this case this sprint will not be visible in board A. Though this issue will not be included in XPTO sprint at all.
Hi Alexey,
Thanks for your feedback.
Yes, we can manually edit the issue field "sprint" and remove the sprint itself, but we are looking for a solution each not requires manual operations.
Would it be possible to tweak the Move functionally of JIRA, through script runner for instance ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is possible with ScriptRunner. You can hide the Move button and make your own button instead. Or you can see if an issue was moved, then clear the sprint field.
But I do not have a ready made code for this requirement, unfortunately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Perfect. We will try that, and post here feedback :)
Thank you for your insights
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are most welcome!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.