Hello friends,
Here's my use case: Want to set up a form for business to request a project. Want that form to replace our current project charter document (as these require the same fields). Need a document to present to executives for approval, prior to launching project.
1. Can you configure a confluence template to create a jira issue and populate it's fields? (this way we can keep the confluence doc for approval)
2. OR, Can you configure a jira issue to create a confluence document, filled with all the fields of the jira issue?
3. OR Can forms from Jira Work Management be saved as a PDF or confluence page once filled / submitted?
Many thanks to the community, y'all are the best!
Hi @Shae Theaker ,
Welcome to the community!
Very interesting use case this with Executives needing to review and approve a set of data (project charter).
I think it is good to have a think about the necessity of duplicating the information in Jira and Confluence. We would like to avoid having a piece of data (f ex project budget) changed in the Confluence page after being approved in Jira? Moving data back and forth between Jira and Confluence needs to have a clear purpose.
Do you want to involve Jira for the purpose of tracking the approval process and/or the action to launch a particular project? Then after launch the Jira ticket is no longer in use and can be archived?
You could work with approval process in Confluence - see inspiration here
For the solution options you asked about
1. In Confluence premium you have confluence automations that has a "Create issue in Jira" - action to utilise
2. Check out this how to for creating confluence pages from a Jira issue.
3. There are form settings per form, to use for storing a PDF to the jira issue each time a form is completed, see here
All the best
Lisa
Hi there Lisa,
Thanks for the warm welcome and thanks so much for your help.
I'd like to explain the use case a little better for those who may be struggling with a similar issue. My organization would like to perform as much of the project management lifecycle as possible in Jira. We currently have a tool set up which ingests a digital form and populates a fillable PDF, which becomes the project charter. This charter is then sent to executives for approval and once approved the project manager ingests that information into the current project management software.
Our goal is to replicate as close as we can, that project intake into Jira for a full and complete automated lifecycle. To accomplish this, as you suggested, we will utilize option 3 that you provided. This allows for an easy form intake, document capture of that form and automated approval process, seamlessly transitioning into the project workflow.
Thanks a million Lisa!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just glad to be of help!
If you want to keep it in Jira as much as possible and if you are open to skip the whole PDF file procedure, you also can build up fields and workflows with statuses for review and approve and limit those to be executed by certain individuals. All approvals will be tracked in the issue history.
If you mark this as answered you help the community to filter on unanswered questions.
all the best
Lisa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.