nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moving issues within a sprint, duplicates the sprint as well

tiagosantiago

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

Accepted answers

All comments

Alexey Matveev

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.

tiagosantiago

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 ?

Alexey Matveev

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.

tiagosantiago

Perfect. We will try that, and post here feedback

Thank you for your insights

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software