My team creates Product Requirements in Confluence (using the Blueprint template). We then create Jira tickets using the auto create function from the product requirements/user story table in the blueprint. The rows in the table are then created in Jira (as tickets) and associated to the Epic tagged in the Product Requirements Blueprint.
Any solutions to these two issues would be appreciated!
For issue 1, the JIRA Issues macros should be added to the table when you hover over the table and create JIRA issues. Here is an example: For issue 2, the JIRA issues are independent of the updates on the Requirements table, once the JIRA issue is created. So the behavior you are seeing is expected.
Are you seeing a link back to the Confluence page in the Issue Links section of the JIRA ticket?
Are you a whiz at handling tickets and looking at how you can further optimize your workflow with automation? Do you tackle detailed customer support questions while simultaneously getting flooded wi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs