I goofed. Don’t do what I did.
We found a bunch of Bug issuetypes added to our Sprinting Project. We’ve recently decided that bugs go through the Product Team (another Project) first for approval then each Sprint, we move a bunch in bulk to the Sprinting Project’s Backlog.
So…I moved the Bug issues over to two other projects. What I failed to do was to compare screen schemes between the two!!!
Result: QA team is Slacking me wondering why the Steps to Reproduce field disappeared. Oops.
Luckily, as soon as I heard that a field was missing I knew it was related to a move from one Project’s screen to another’s.
Also luckily, the field in question had a field configuration of Global (all Projects) so I knew the data was still there.
So to outline:
- I needed to move ProjectA Bugs elsewhere.
- I discussed the move with our Tempo Manager (if you move an issue, you move the time logs); and QA Leads
- Target Projects were approved
- Should have brought up Create, View, Edit Screen Schemes for source Bug and target Bug issuetypes.
- Should have compared screens and updated accordingly
Some people say that it should have been tested in a test Jira environment first. Yes, 1) if the instance was up to date and 2) if it were to be tested by QA before release
We all do what we can and learn from our mistakes; hopefully you’ll learn from mine.
If you want to learn about more mistakes (and learning experiences) I recommend Jira Strategy Admin Workbook by Rachel Wright (not a commissioned link so I don’t have to disclaim that link)
Ever make mistakes in life? Let’s make them birds. Yeah , they’re birds now…. see Amazon link of a Bob Ross t-shirt.