-
Suggestion
-
Resolution: Unresolved
-
0
-
1
-
Confluence content should be embeddable on Jira issues but only editable in Confluence. This makes the Confluence page the source of truth for the content, but users don't need to leave Jira in order to view it.
For example, I have a definition of Ready and Definition of done all in the same confluence Page.
It would be great if I could display the text relevant for the Definition of done in the description of the Jira ticket.The Text should at least be fetched when I create the Jira ticket:
Thought would have to go into whether the text should continuously update or not, since that could mean that specifications suddenly change without anyone knowing, and old tickets would suddenly show texts that weren't true or relevant yet when the ticket was first created.
Ideally you could do both, a one time fetch or a fetch that continuously updates each time the Jira ticket is opened.
Original Description
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
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-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
Hi 7b56c155cd64
No one out there is constantly monitoring their email for updates to these suggestions because they sit for soooo long. You can't expect to get an outpouring of comments and information within just a short amount of time when the suggestion has been open for almost 10 years.
I mentioned that all you need do is comment on the closed issue and it can be reopened. I have done that now.
Would you be able to expand on how you would ideally like this feature to behave on the Jira Cloud side? If I understand correctly, the request is for Confluence content to be embeddable i.e. viewable on a Jira issue, but not editable there. Is that right?
Wow, waiting just 7 days after such a vague comment then closing the case. That's a new one. How has the product changed since this issue was created to allow for a single source of truth for requirements to be identified and shown within the Jira system? Perhaps by explaining how Jira and Confluence have changed to provide the functionality identified, then people would be more open to the changes. No one out there is constantly monitoring their email for updates to these suggestions because they sit for soooo long. You can't expect to get an outpouring of comments and information within just a short amount of time when the suggestion has been open for almost 10 years. Atlassian has waited almost 10 years to show any interest, and then you expect us to respond in less than a week?
As I did not receive any responses to this comment I am closing this ticket.
If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.
Hey fa0bd1444987 and other watchers of this issue - I believe the product has changed a bit since this ticket was created. Would you be able to expand on how you would ideally like this feature to behave on the Jira Cloud side? Thanks!
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. Since this issue has been idle for a bit, lets breath some life into it.
Like prior comments, Confluence is brilliant for the construction of content - collaboration is now common place and we have review and approve workflows built to establish baseline ready.
Revisions to this content after the JIRA issue is created is often neglected. Project teams work entirely from JIRA, only stakeholders and the product owner / BA are active in Confluence so a synchronization between the two – always showing the current Confluence content is going to be a huge win. I've tried the scripting work around, publishing Confluence as plain text to an external URL, changing behavior to work from Confluence first and embed JIRA within Confluence. All are falling short.
Anyone found a more robust / reliable solution yet?
I like this idea a lot, but I'm a little worried about how history tracking (and notifications) would work. Would edits to the embedded Confluence page show up in the JIRA ticket's history log? Would it respect the different permissions between the two tools? There's so much data to keep tabs on, and it sounds like Atlassian wouldn't build this if it was just a type of 'excerpt' support. Seeing how requests have been implemented in the past, they would work something like this into larger plans for deeper JIRA+Confluence integrations in general. They're not going to build it one way temporarily just to throw all that code away for the "for real" implementation two releases later.
This really feels like a good candidate for a third-party add-on. Businesses that want this would happily spend the extra cash for it.
For example, I have a definition of Ready and Definition of done all in the same confluence Page.
It would be great if I could display the text relevant for the Definition of done in the description of the Jira ticket.
The Text should at least be fetched when I create the Jira ticket:
Thought would have to go into whether the text should continuously update or not, since that could mean that specifications suddenly change without anyone knowing, and old tickets would suddenly show texts that weren't true or relevant yet when the ticket was first created.
Ideally you could do both, a one time fetch or a fetch that continuously updates each time the Jira ticket is opened.
It's a tough one