Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why does moving an issue between projects associate the sprint from the old project with the new one Edited

I use Jira 8.5.5 hosted by Di2E, and I have a major problem with the way sprints are handled when moving issues between projects.  I manage multiple product lines, and occasionally there are tickets that are entered in on the wrong board.

The problem is that if the Jira issue is already assigned to a sprint, that sprint that was for Project A is now also associated with Project B.  There is no way to disassociate it from the wrong project board without causing unintentional harm.  When the same sprint is associated with two projects the following are true:

  • Changing the sprint name on one board changes it on the other board
  • Deleting the sprint deletes it on both boards and all the associated issues are moved to the next sprint (or backlog)
  • Starting the sprint on one board starts it on the other

The major issue is that I never wanted that sprint to be associated with the other project.  Each project has it's own release trains and numbering.  The only way to fix the issue I know of is the following procedure:

  • Create a new sprint on the origin board
  • Move all the issues from the original sprint to the new one (and the sprint goal as well)
  • Move all the issues from the destination board to the correct sprint or backlog
  • Delete the duplicate sprint (affects both boards)

If multiple people are working the backlog, and new issues get assigned to the erroneous sprint, we have to create 2 new sprints and move the issues on each board to fix the problem.

QUESTION 1:

Is there any non-destructive way to remove a sprint association from a project's board?  Barring that, can "Delete Sprint" be redefined to remove the sprint association with a project and on the last association actually delete the sprint?

The current behavior is confusing, introduces too many opportunities to unintentionally screw up another project's backlog.

QUESTION 2:

When moving an issue between projects, can we please strip the associated sprint that should ONLY belong to one project?

This is the real problem here.  It's surprising behavior, and it is the only way I know of to get into a situation where the same Sprint object is associated with boards for two separate projects.  It should be considered a bug.

1 answer

0 votes
Ivan Lima Community Leader Sep 27, 2020

Hey @Berin Loritsch, if you hadn't had a chance to browse similar questions to yours in the community, I will be sharing a few of them for your reference. Therefore, in short, this scenario is a known "issue" raised as a suggestion at JSWSERVER-11992. You can vote for it to be considered in features releases and add yourself as a watcher to receive updates moving forward.

That said, have a look at the following knowledgebase articles that should address the main points of your questions since it is the current JIRA Agile behaviour - although it's not quite intuitive for end-users as stated in the article.

Also, have a look at other similar questions that may provide you with additional insights

I hope that helps,
IL.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

326 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you