Our user is reporting the following issue. Any idea how this could happen?
Over time tickets need to be updated with new priorities, or additional changes however if the "reporter" is someone that is no longer with the company the system will not let you save the changes until you replace the reporter with someone who is still in the system. As a result the entire history of the ticket is altered to show the new reporter as the one who made all the comments in the ticket and reported the issue.
This is a problem because the information of where the issue came from is lost. Currently I am just putting myself as the reporter so the priorities can be updated. But this posed problems because others reading the ticket assume I was the one that logged the issue.
The system should not alter historical comments, or require the original reporter to be changed when making updates to tickets after the person has left the company. This also skews reporting on tickets logged by person.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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