I have PBis that have been created that are now part of other PBI's. I don't want to delete them because I need a record that they have been merged into other projects.
In greenhopper I only have status choices of To Do, In Progress, and Done - I can delete, but that's not going to give me the ability to track these issues.
Help is appreciated.
I believe you need to go in a different way, Franci.
There is that question, if they were moved, how were they moved? Did you just create new issues and cut and paste? Beacuse as Ronny says, any issues that were moved via the move command should not leave copies.
Next, just because you move an issue into the "done" column doesn't mean that it's going to be marked as resolved. The resolution field is complicated. Either it doesn't have any resolution (so it says unresolved) or it does have resolution. If it does have resolution, then it displays a specific resolution, such as Fixed or Duplicate. You can configure your system with custom resolutions if you'd like.
If I was customizing your JIRA setup, I would make sure that when you marked an issue as "done" that a transition screen would pop up and ask you what the resolution was. Was it fixed? Was it a duplicate? Was it migrated into another project? Creating your own custom field for this behavior is definitely a bad idea. If you want to search against the resolution, that's very easy to do in JIRA.
you could move them to the DONE column, which automatically sets the status to done and also marks the issue as resolved (resolved date will be populated).
If you configure your agile board (click on the gear icon in the upper right corner on your agile board), you can configure your columns and their mapped statuses.
You should be able to pull in the resolved status separately if needed.
But generally, if you move an issue to another project, they should not show up on your agile board any more, unless you pull in several projects for your board.
A good way of filtering out unwanted issues is to change your filter for the agile board.
You can do so using the "configure" link again (gear icon).
Hope this helps.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs