If traceability is also important for you, you can take an snapshot of your requirements by exporting them from Confluence into a PDF file, create a version on a document repository (like Subversion) to track changes between those snapshots (snapshot1, snapshot2,...) and use DocMiner to create JIRA issues from the document directly (related to texts and images).
DocMiner guarantees the traceability between JIRA and the requirements in the documents, automatically opens the right version of the document and scrolls to the requirement from within JIRA. It also can compare the PDF snapshots, show the differences between the document versions in a synchronized way, see how the changes impact on your current JIRA issues and import issues (requirements) fro older versions to the newer if you want to consolidate all your requirements spread among several document versions into a single major requirement document version.
Bored in a useless meeting? Don't worry, DocMiner works in the go, therefore you can use your smartphone to capture requirements from documents and asign them to developers and track the progress on JIRA from the document itself on your smartphone, from everywhere and at any time.
Furthermore the tracebility, DocMiner provides a lot of contextual information to developers when the open the issue on JIRA as it is able to provide bi-directional traceability from documents to JIRA issue and vice-versa. Hence, furthermore traceabilty it also improves collaboration.
So, briefly, you can use Confluence as a distributed document editor (Wiki) to collaborate in the content creation pahse and DocMiner to collaborate in the analysis and development stages and keep the traceability.
Unless you have hundreds of them, copy-and-paste is your friend. If you do have hundreds, then you have a couple of easy options:
1. There is a CSV importer for JIRA. It does what you think it would. You'd have to massage your epics and stories into comma-separated format.
2. For a little more flexibility you might try massaging your stories into Jelly tags. Specifically, the CreateIssue tag will help you. In JIRA, the Administration area includes a Jelly Runner, which allows you to execute the tags that you have created.
Atlassian Command Line Interface can help with the automation both out of Confluence and into JIRA. But a lot depends on how the data is formatted. Likely the Confluence data is going to be storage format :(. I would suggest it would be better/easier to create JIRA items that link back to the Confluence pages for the details - this is a common approach as Confluence is often better for that kind of documentation anyway. You can also link from Confluence to JIRA using the same automation that creates the JIRA items.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
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