I know this is an ancient question, but it's worth thinking l about permissions and who has access to your 'projects'.
You might want to consider an 'HR-internal' project, with restricted access permissions and move that issue there instead.
That way you don't lose the issue and it's resolution, but you restrict who can see it.
(This might take someone with admin priveledges to set up for you)
Great idea: Project-X and Project-X-Archives, where only project admins have access. Project admin can move the resolved issues to the Archives at a pre-determined point in time, either by automation rule or manually, say as a sub-segment of scrums -- covering what will go to archive and what needs continued visibility.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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