Is there an easy way to track when a user changes an issuetype without creating another custom field?
# Tester submits issue as a Bug in JIRA
# Developer disagrees and changes to a Story issue type
# When an issue type is changed, we should be able to find using a JQL query like
issuetype WAS IN (Bug)
There was a support case raised for this, so I'm updating this question with the suggested resolution in case anyone else happens to find it.
Currently WAS isn't supported for IssueType, however you can kind of workaround this with a plugin and a different solution.
Unfortunately, this won't stop users from changing it during a bulk or normal move and if it is changed more than once the first value will be overwritten. However, it can be used as a workaround for all other scenarios.
I believe there is a read-only custom field type within the JIRA Importers Plugin that could be used for this purpose. It is however not designed for this, so may not be the most ideal workaround.
I think that I found the issue! Although it was logged as an improvement:
I provided some use cases back in June and then the issue was resolved in September as a "we're not going to improve this area".
What? Never? I think that the issue should have been left open... at least in order to see whether it would gather more votes and to let people make comments. People can still make comments now of course... but what's the point?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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