Hi All,
So i have the automation for when an issue is moved from in review to in progress, which is one stage.
but my question is, is it possible to find the user from a 2 stage difference, so for example, in my project we have the below set up
if I wanted to transition from QA to in progress, but the issue had been assigned to someone else during in review, would it be possible to get the information out of the issue history to get the name of the engineer during in progress and reassign it to him using automation.
thanks
Without using an addon, you can only check on who the current assignee is, not who the assignee was when the issue was in a previous status, in fact the answer by @Pasam Venkateshwarrao showing the transition history is provided by an addon.
To clarify this, there is a changelog maintained for issues, but as per the snippet copied from https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ only a few properties are available from the changelog and assignee is not one of them.
You could get round this by adding in a number of new custom fields for each status and storing the assignee in the appropriate field e.g. 'QA Assignee' then using that field to update the assignee at a later time.
Used with: any triggers that edit an issue.
This smart value accesses the changelog, and a list of changes for each field. For example, when an issue is transitioned you can see what status the issue transitioned from.
Learn more about using smart values with sections and lists.
{{changelog.summary}} - Changelog information for the Summary field.
{{changelog.issuetype}} - Changelog information for the Issue type field.
{{changelog.status}} - Changelog information for the Status field.
Ok Thanks Stephen, I guessed it might need to be custom fields, as I couldn't find any other way to do it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ok, but how can i pull that information out for a new automation flow
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@jeff_trotman please try with post functions to achieve this in inprogress transition
refer the doc:https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/
Hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community,The issue transitioned from QA to In Progress you can see who moved the status in the issue Transition
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.