-
Suggestion
-
Resolution: Tracked Elsewhere
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Steps to reproduce:
1.) Create a requirment page in Confluence (Blueprints).
2.) Modify the page title to "Test".
3.) Insert a Jira Issue with the Jira Issue Macro somewhere in the template.
Problem: I have to copy the page title of the requirment manually to the summary of the jira issue. It would be much more comfortable if the macro could use page title of the requirement as default for the jira summary.
Another really useful feature would be a macro to create a button "Create Jira Issue" on the requirements template. The jira issue could be generated without any interaction of the user by configure this button to use a special jira project and a special issue type e.g. requirement. The summary and the description could be generated with the content of the requirement blueprint.
There is to much work needed (clicking and user interaction) to create an jira issue in my opinion.
- incorporates
-
- Closed
- relates to
-
- Closed
-
- Closed
[CONFSERVER-29568] Copy requirement page title (Blueprints) automatically to Jira Issue Summary
Achim Winkler
added a comment - It seems to be the right direction but i miss the configuration of the create Jira issue macro, to have less work to create the issues.
Achim Winkler
added a comment - It seems to be the right direction but i miss the configuration of the create Jira issue macro, to have less work to create the issues. Thanks for the details, Achim. I wonder if a feature like this: CONF-29154 for JIRA would be helpful for you. So think of creating a requirements document, then having some grey instructional text that says "Create JIRA issue for this requirement" which simply opens the JIRA issue dialog, with the create selected and the page title already populated...thoughts? That sounds like it could help you with (1)
Achim Winkler
added a comment - I know this already, but this is not comfortable. The point is that many clicks are needed to create such an issue. You have to click on insert, to choose the Jira issue, to click on Create new issue and to "reenter" the summary (the macro could use the page title automatically). If it is the first issue, you have to choose the project, the issue type and so on. There should be a fast way to insert such an issue, like a simple preconfigured click button.
The use case is the following:
1.) We want to create a lot of requirements for a project. Each requirement should be on a single confluence page.
2.) Now we have to decide which features we want to implement. Such features should have tickets to track the progress in Jira or to split the feature into working packages (each working package has its own ticket).
Achim Winkler
added a comment - I know this already, but this is not comfortable. The point is that many clicks are needed to create such an issue. You have to click on insert, to choose the Jira issue, to click on Create new issue and to " reenter " the summary (the macro could use the page title automatically). If it is the first issue, you have to choose the project, the issue type and so on. There should be a fast way to insert such an issue, like a simple preconfigured click button.
The use case is the following:
1.) We want to create a lot of requirements for a project. Each requirement should be on a single confluence page.
2.) Now we have to decide which features we want to implement. Such features should have tickets to track the progress in Jira or to split the feature into working packages (each working package has its own ticket). HI Achim,
Thanks for the details, did you know you can already create a JIRA issue from a Confluence page? http://cl.ly/image/3938102P2V1O
All you need to do is insert > JIRA issue and select "Create new issue" tab. Is that what you are after?
Out of curiosity why do you want this? Is it because every requirement has an issue in JIRA?
thanks. I've linked it to the issue as it will be ultimately implemented from the linked issue first. Regarding the configuration, we will try and reduce that friction.