Transition Jira issues to a new status when a page's status changes

[Marc - Devoteam]

When a page's status changes to the status you specify (i kept the ootb page statuses)

So when the page status changes to "Rough Draft", I want the linked Jira issue (Confluence page is linked from the Jira issue) to tranistion.

This to status draft.

In Confluence automation there is a ootb brach option for Jira issues. this requires to set a JQL clause to find the issue, but it can find multiple issues.

I don't want all the found issues to transition, only the linked issue(s), here is the problem.

Is there anyone to help or has an idea.

Automation rule:

Audit log:

 

[Darryl Lee · Accepted solution]

Hi @Marc - Devoteam - can I suggest this endpoint:

https://YOURSITE.atlassian.net/wiki/rest/jira-metadata/1.0/metadata?pageId=YOURPAGEID

That should return the Jira Issues in the breadcrumbs.

(Although there are issues with the Jira Issues breadcrumb if issues are later unlinked from Confluence pages:

• Confluence 'JIRA links' not updated when 'JIRA Issue' macro is removed - feature - not sure why it is a "feature"
• Pages linked in Jira are not updated after removing Jira Macros from Confluence - bug
• Removing Jira Issue from Confluence page doesn't update Jira Links metadata panel - bug

Fun stuff!)

This endpoint is (of course) poorly documented. I think it's an old server endpoint, in fact. 

• The rest api GET http://{myConfluenceServer}/rest/jira-metadata/1.0/metadata 
• Get all Confluence pages that have JIRA links on them 

[Marc - Devoteam]

Hi @Darryl Lee 

Thanks, I will look into this.

[Marc - Devoteam]

HI @Darryl Lee 

I found a solution your pointers helped.

I will write an article on this on the community.

Thanks.

[Marc - Devoteam]

Hi @Darryl Lee, @Kelly Arrey and @Harrison Ponce 

Here is the article with the solution I used.

Confluence-automation-to-transition-a-Jira-work-item-based-on-page-status 

[Kelly Arrey]

Hi @Marc - Devoteam,

I found this - thought you might want to vote for the Suggestion:

Just me thinking out loud, but can you come at this from another angle? Parse the linked ticket number from the Confluence page and than pass it to Jira? This page seems to suggest that you could transition the Jira ticket in a Confluence rule?

HTH, 

Kel

[Marc - Devoteam]

Hi @Kelly Arrey 

Thank you.

I know this, this is also already in my automation, but the issue is you need to provide a JQL clause in this action.

This finds issues based on the JQL not the issue related to the Confluence you change. So then all actions set will act on all found issues, not just the issue linked with the Confluence page.

Also the Jira issue is not set on the page vai a macro or smart link, but the Confluence page is linked from the Jira issue.

I don't use a jira issue macro on the page as the page is also auto created based on the linked Jira issue on creation.

My issues is that when a Jira issue has a linked Confluence page, the Confluence page shows the linked Jira issue in the breadcrumbs section on the page.

I only want this issues or issues to be impacted, not all the issues found in the JQL provided in the Jira branch on the Confluence rule

[Kelly Arrey]

Hi @Marc - Devoteam, yup I get what you're trying to do. Sorry I don't have any more ideas. 

[Marc - Devoteam]

Hi @Kelly Arrey 

The body of the Confluence page doesn't show the Jira issue info based on  how it's linked via a Jira issue.

I don't want to be forced to but a macro or smart-link in the page, otherwise this automation option between the products serves no use in my opinion.

but thanks anyway for sharing your thoughts