-
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
[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
| UIS | Original: 1 | New: 0 |
| Description |
Original:
{quote}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.{quote} h3. 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. |
New:
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.
{quote}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. {quote} h3. 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. |
| Description |
Original:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-38416]. {panel} 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. |
New:
{quote}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.{quote} h3. 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. |
| UIS | New: 1 |
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?
| Resolution | Original: Incomplete [ 4 ] | |
| Status | Original: Closed [ 6 ] | New: Gathering Interest [ 11772 ] |
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?
| Resolution | New: Incomplete [ 4 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
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.
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