We have issuetypes that change from one issuetype to another depending on how customers report certain issues. They can move from a troubleshooting issue to a defect for instance once they can be fully reproduced. since we use metric based on created date and issuetype these sometimes are not included accurately in historical data if the issuetype changes.
We would like to set a couple of fields suchs as previous issuetype and issuetype date changed in scripted of calculated fields if this is possible that way we can include these properly in metrics
Thanks
Issue type changes are recorded in the history, so yes, you can write a scripted field that would go back through the history and find and expose issue type changes.
Nick,
thanks assuming I would need to do something like
import com.atlassian.jira.issue.history.ChangeItemBean
def changeHistoryManager = componentManager.getChangeHistoryManager()
def rt[0]
changeHistoryManager.getChangeItemsforField(issue, "issuetype").reverse().each {ChangeItemBean item ->
if (item.fromString == "TroubleShooting") {
rt << "yes"
}else
rt << "no"
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.