Jira/Confluence automatic documentation

[Sarah Damag]

Dearl all,

I would need to use Jira and Confluence to automatize :

• creation of Feature page when creation of Feature in JIRA - Done
  • if I change work type name in Jira, it is changed in Confluence --> Possible ?
  • if the Confluence page name is changed, feature name is changed in Jira.
• creation of Story page when closing of story in JIRA. - Done
  • Story page to be classified below Feature page of Jira story's parent --> Possible ?
  • if something is changed in Confluence page --> no impact on Jira

Do you know if all this workflow is possible ? Do you know another way to ease automatic documentation (not to open each story 1 by 1)

Thank you,

Regards,

Sarah 

[Lukas Nicolai_Seibert]

Hi @Sarah Damag ☺️, welcome to the Community! 

If you’re open to using a third-party app, AutoPage could be a great solution for automated documentation.

• With AutoPage, you can automatically generate Confluence pages directly from Jira issues. For example, as you mentioned, the trigger could be a status change like “issue = done.”
• Changes from Jira to Confluence would also stay live and in sync.

You can find us at the Atlassian Marketplace ➡️ https://marketplace.atlassian.com/apps/1218503 

[Sarah Damag]

Hi Lukas, I would rather use native features of Jira to avoid dependency to another tool.

[Sarah Damag]

Hi Varsha, 

Thank you for your reply !

First question - I am expecting a change of the summary of the issue.

Assumptions:

- I have created a Confluence page from a Jira issue,

- This Confluence page title is equal to the Jira issue (I automated this)

For now, there is no link between the Jira issue and the Confluence page, when I make some change on one, it is not reflect on the other. I would need : when I change the summary of the Jira issue, this new summary becomes the title of the Confluence page (which already exists). This behavior would depends of the issue type.

First question second bullet point - Yes exactly

[Varsha Joshi]

Hi Sarah,

Welcome to the community!

Quite an interesting automation :-)

For your first question - are you saying change to the summary or the issue type? If it is change to the issue type then could you clarify what is that change going to be?

First question second bullet point - are you saying if the page title is changed that needs to be reflected in the Jira by updating summary?

[Sarah Damag]

Hi Varsha, 

Thank you for your reply !

First question - I am expecting a change of the summary of the issue.

Assumptions:

- I have created a Confluence page from a Jira issue,

- This Confluence page title is equal to the Jira issue (I automated this)

For now, there is no link between the Jira issue and the Confluence page, when I make some change on one, it is not reflect on the other. I would need : when I change the summary of the Jira issue, this new summary becomes the title of the Confluence page (which already exists). This behavior would depends of the issue type.

First question second bullet point - Yes exactly