In JIRA, we often move isues from one project to another.
Once the issue is moved, we can always trace the source project by clicking the history tab on the view issue screen.
My question is we do not want to reveal this information to our users that the issue was moved from which source project.
Can this be achieved?
Not without code. The point of an issue tracker is that it keeps a history. Moving issues between projects is part of the history, so it gets logged and tracked.
Your coding approaches are probably:
Unusually, I'd recommend the last one. My normal instinct is to avoid changing the core of Jira for support and upgrade reasons, but in this case, amending the issue view is probably the most simple code change, and it avoids damaging the data - it's still logged, just not shown. It avoids additional processes and data writes too.
That's always an option with direct access to the SQL, but you've got two instant problems - first that you need Jira offline while you run the SQL, and re-indexing is needed after that. Second, you can only do it for existing issues, if anyone moves an issue again, you'll need to stop, run SQL, reindex every single time.
Seriously though, don't do it. The hack in the database will literally destroy the issue history. All of it. Gone. Forever. In implementation terms, you might as well go back to shared spreadsheets or post-it notes which can lose your history really quickly.
Please. Stick to option 4 on my list above - hide the data, don't destroy it.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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