Hi @Kishore Kumar Gangavath , while JQL has the CHANGED keyword it isn't supported for Issuetype. One option would be to use a custom field and automation to capture when an issue type changes. The way this would work is that you would trigger on the issuetype changing in your automation rule, then setting your custom field to true, or whatever value you want. You can use JQL to query that field. In my opinion, this is a bit awkward and heavy handed. The other option is to look to the marketplace as there are add-ons, that would support this requirement.
Hi @Jack Brickey ,
Thank you for the information. The automation will capture for the new issues. I need to know already modified issues. If am wrong kindly provide me an automation rule.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are correct. For history consider addon or the APIs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can get past IssueType changes with Issue History for Jira. My team developed the add-on as a journal for all past changes. You can filter issues by projects, sprints, assignees, date ranges, etc.
You can try how it works for you with 30-day free trial. Let me know if you have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.