Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to get the issue 'history revision' in Jira Automation?

Inna S
Contributor
February 19, 2023

Hi, 

our business process calls for propagating changes made to one issue on to another issue.

To help people understand why a change was made to the issue by the automation, we used to indicate the 'change revision' of the original issue that triggerred the change there.

The history of changes was displayed with the revision number, so we could have an audit record as part of any automated transaction, that would say 'triggered by the revision X of the issue Y'.

Not only Jira UI displays several field changes as separate transactions in the issue history, but I do not see the 'revision id' of the change in the 'changelog'.

Can you help?

Thank you.

 

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 19, 2023

Hi @Inna S 

I am unclear what you mean by the following: 'revision id' of the change in the 'changelog'.  Perhaps you could clarify that so the community could offer suggestions.

Within an automation, I suppose you could add comments/edit an audit field to describe the source of changes.  The current issue change history will already show both that the rule acted upon the issue and the changes made, however it will not show things which are in the automation audit log, such as the issue/condition which triggered the rule.

Kind regards,
Bill

Inna S
Contributor
February 19, 2023

@Bill Sheboy 

In the picture revision number is marked in red. I'm looking for this number in Jira.
Also, in this system I use as a reference, the description often lists several fields if they were changed at once.
Thank you

Revisions.jpg

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 19, 2023

That information appears to be from some other tool, or an addon app to Jira Cloud.

If it is an addon app which has added custom fields to Jira, you could find the smart values for the fields using the information in the how-to article below, and then reference them in your automation rule.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Inna S
Contributor
February 20, 2023

@Bill Sheboy this is not from Jira. It is from a different system. I'm looking for the analog of it in Jira and do not see it.

Not only Jira history lists 3 field changes made at once as separate history entries, it also does not dispplay the history revision ID.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2023

Thanks for clarifying that information.  There is an id for each change in the issue change log history, and I believe you would need to call the REST API to get it:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-changelog-get

Inna S
Contributor
February 20, 2023

Yeah, @Bill Sheboy , I saw this.

But the number does not make any sense as it appears to be 'global' and not a conventional 'revision' number for specific issue.

And it looks like I have no way surface it in the history section for a user to see.

The original intent is to help user understanding why the current issue they are looking at has a specific field changed. This field change can be in the middle of the issue history. 

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2023

Other than the issue change history (in the UX and via the REST API) those are the only built-in things.

Perhaps check the marketplace to learn if there is an addon app which has what you are looking for in this type of tracking: https://marketplace.atlassian.com/

Inna S
Contributor
February 22, 2023

Thank you @Bill Sheboy .

As always with Jira, the basic capability is either not available or might be obtained for extra $$ from yet another 3rd-party vendor with all the troubles of it.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events