-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
2
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
We have both Jira and Confluence in house today.
Our requirements elaboration process is more or less like this:
Whiteboard > Balsamiq > Axure > Jira epic > Jira user stories > Development > "Move content to Confluence for both description of business rules as well as the user manual".
Some time after release the improvements are registered. Minor adjustments to make it just a little bit more user friendly, changes to the business rules, etc. This is normally done in Jira. However, we see very often that we forget to update the business rules section in Confluence.
So we would like to change the process a little - to get down the requirements in Confluence first before we start creating Jira issues. And when we start creating Jira issues, we only reference certain placeholders or similar on a specific Confluence page. This will ensure that the content in Jira is updated continuously as there is only one true source of descriptions.
This "one source" idea is used by eDevTech with their product InteGREAT that manages requirements gathering and management together with TFS.
- is related to
-
- Gathering Interest
- relates to
-
- Closed
-
- Gathering Interest
- links to
[JRASERVER-38416] As a user I would like to include specific content from a Confluence page in a Jira issue so that I only have one source for requirements descriptions
Please build this feature! It would help me so much for today and tomorrow's upcoming work this year.
We use JIRA/Confluence Cloud and we have a workflow that keeps documentation pages for specific long term information. When we create a Jira issue that references the page/table we would like for that long term information to be shown in the Jira issue for easy referencing. This would be a huge help to our workflow, also updating the table/page in Confluence from the Jira issue would be awesome as well!
John Eliopoulos
added a comment - Please build this feature! It would help me so much for today and tomorrow's upcoming work this year. 
John Eliopoulos
added a comment - Please build this feature! It would help me so much for today and tomorrow's upcoming work this year. community of practices often have desired ways of working documented in confluence. When a certain Jira story involves one or more of this recommendations, I would like to add said page(s) onto the story description itself. I don't think a custom field will work in this instance as I most likely want to add different pages depending on requirement. it would be better if its tagged in description and maybe when story/task/epic is closed, the version of that embedded page is saved.
This would be super useful:
1. Create Custom Field in Confluence.
2. Create Custom Field in JIRA.
3. The Custom Field in JIRA can be configured to show the value that is from the Custom Field in Confluence.
Also super interested--and frankly a little shocked it's not supported. It's seemingly a simple integration once you have both server-based products linked so why no ability to surface Confluence content in JIRA? I would absolutely LOVE to be able to have power users author guidance that's shown on an issue (e.g., in sidebar), ideally with the ability to target what's shown on different statuses. Can someone at Atlassian comment as to why this years-old issue isn't getting any traction?
Joel Tablante
added a comment - I am also interested in this feature as it would help standardize workflow process referencing confluence standard documentation that can be maintained in one central location.
Joel Tablante
added a comment - I am also interested in this feature as it would help standardize workflow process referencing confluence standard documentation that can be maintained in one central location. I am also interested in this feature. The teams I work with would like to manage a Definition of Done and Definition of Ready at the team's Confluence page and then when creating and updating an issue of a certain type (ie: epic or story or feature), show the team's definition of ready and definition of done confluence excerpt in the Jira Issue being created or updated. Would like to also associate the excerpt to the Jira team. This way if you move the issue to another Jira project, the correct definition of ready and done shows in the Jira ticket. Looking to maintain the text in Confluence and display in JIRA.
Marie Drahorad
added a comment - - edited I am also interested in this feature. The teams I work with would like to manage a Definition of Done and Definition of Ready at the team's Confluence page and then when creating and updating an issue of a certain type (ie: epic or story or feature), show the team's definition of ready and definition of done confluence excerpt in the Jira Issue being created or updated. Would like to also associate the excerpt to the Jira team. This way if you move the issue to another Jira project, the correct definition of ready and done shows in the Jira ticket. Looking to maintain the text in Confluence and display in JIRA.
Hello, I'm looking for this now years later and still there seems to be no solution to really have Confluence as the Single source of truth and see that in the Jira tickets.