Understanding Your Jira Automation Requirements
Clarifying Your Vision for Automatically Generating Epic, QA, and Certification Timelines
Key Highlights
- Automated Epic Creation: An Epic is generated upon creation of an Initial Game Production issue, acting as a parent to that issue and subsequent related tasks.
- Generation of QA and Certification Timelines: The automation rule will create dedicated issues for both QA and Certification timelines, linking these as children under the Epic.
- Audit Logging and Customization: Each automation step includes an audit log with explanations and can incorporate dynamic naming, field mapping, and issue linking techniques.
Detailed Analysis and Clarifications
Your requirement centers on a multi-step automation process in Jira where the creation of an "Initial Game Production" issue triggers a series of actions:
Workflow Overview
The envisioned workflow includes the following crucial steps:
- Automatic Epic Generation: When an "Initial Game Production" issue is created, the system automatically generates an Epic. This Epic is intended to become the parent not only of the triggering issue but also of any subsequent issues or tasks that are generated in this automation sequence.
- Creation of QA Timeline: An issue representing the QA Timeline is created during the automation process. This timeline could be formatted as a Task or Story, and it needs to be linked under the Epic.
- Creation of Certification Timeline: Similarly, a Certification Timeline issue is also automatically generated and linked under the same Epic.
- Audit Log Inclusion: Each automation action is recorded through an audit log, which not only records the activity but also provides explanation details for troubleshooting and transparency.
Key Points Needing Clarification
While your description is quite clear, a few key points and questions need to be addressed to ensure the automation works exactly as you intend:
1. Linking the Triggered Issue
Should the Epic that is generated automatically become the direct parent of the user-submitted "Initial Game Production" issue? This involves linking the initial issue to the Epic so that the Epic is visible in the "Epic Link" field in Jira.
2. Issue Type and Structure for QA and Certification Timelines
Do you wish these timelines to be created as standard issues (for example, Tasks or Stories) or as subtasks under the Epic? Knowing this will inform the field mapping and linking procedures in the automation rule.
3. Dynamic Naming and Field Customization
Would you prefer the Epic name to be dynamically generated—perhaps incorporating elements from the triggering issue’s fields (such as its summary or project code)? Additionally, are there specific fields, such as due dates, labels, or assignee information, that must be automatically set for the QA and Certification issues?
4. Audit Log Details
The inclusion of an audit log with explanations is an important feature. Can you clarify whether each action’s explanation should simply log what happened, or should it also reference specific field changes and conditions met during the process? This will help determine how detailed the audit log entries should be.
Automation Implementation Strategy
To ensure the automation process meets your requirements, consider these steps for implementation:
| Step | Action | Details & Configuration |
|---|---|---|
| 1 | Trigger | Select the trigger "Issue Created" and set the condition for issues of type "Initial Game Production". |
| 2 | Create Epic | Use the "Create Issue" action to generate an Epic. Populate key fields dynamically using smart values, such as referencing the summary of the initial issue. |
| 3 | Update Triggered Issue | Set the "Epic Link" field of the "Initial Game Production" issue to the newly created Epic’s key. |
| 4 | Create QA Timeline | Generate a separate issue (e.g., Task or Story) for the QA Timeline, linked to the Epic. Consider using custom fields if needed. |
| 5 | Create Certification Timeline | Create an additional issue for the Certification Timeline, properly linking it to the Epic. |
| 6 | Audit Log Creation | Add actions that record/log each step of the automation. You can include descriptive commentary for transparency and troubleshooting. |
Potential Follow-Up Questions
- Should the automations include validation steps? For example, checking if a similar Epic already exists before creating a new one.
- Are there any notifications required? Should team members be alerted when the Epic and associated timelines are created?
- How are field mappings handled? Are there pre-defined templates or fields that must be replicated across the Epic and timeline issues?
- Do you require any further segmentation within the timelines? Such as different statuses or milestones for QA and Certification tasks.
Next Steps for Your Automation Setup
Based on the above analysis, your automation setup should clearly define the exact relationships between the issues. The Epic will effectively serve as the container, and once created, additional issues (QA and Certification timelines) are generated and linked under this Epic automatically. Here is a concise summary of what you envision:
Summary of Your Requirements
When an "Initial Game Production" issue is created:
- An Epic is automatically generated with a dynamically generated title that may include aspects of the initial issue.
- The triggering issue is linked to the Epic as its child, establishing the hierarchical relationship.
- Two additional issues representing the QA Timeline and Certification Timeline are created and linked under the same Epic.
- Audit logs are created at each automation step to provide detailed explanations for record-keeping and troubleshooting.
Your Questions Answered
To directly address your query: Yes, the automation rule you have set up seems to be designed to meet these requirements. However, the success of such automation will depend on the following:
- Clear identification of issue types (Epic vs. Task/Story) within Jira.
- Accurate configuration of the "Epic Link" field to ensure that the Epic becomes the parent of all related issues.
- Dynamic field mapping to propagate necessary attributes such as summary details, due dates, and assignees, if required.
- A robust audit logging mechanism that captures each step and provides an explanation for debugging purposes.
Conclusion and Final Thoughts
Your approach to automating the creation of an Epic along with QA and Certification timelines within Jira is well-conceived. The automation rule is designed to trigger upon the creation of an "Initial Game Production" issue, generate an Epic, and then automatically create two associated issues that are linked underneath the Epic. Integrating an audit log with explanations at every stage ensures that the process is transparent and easy to troubleshoot.
Before finalizing your setup, consider reviewing the field mappings and linking configurations to ensure that the Epic truly functions as the parent for both the triggering issue and the two additional timeline issues. Answering the clarifying questions regarding issue structure, dynamic naming, field customization, and the desired level of audit log detail will further refine your automation process.
If you have any additional requirements or specific scenarios (such as handling duplicate issues, sending notifications, or configuring custom fields between the Epic and its children), now is the right time to incorporate these details into your automation rule. Your current setup stands on solid ground, and with these fine-tunings, your automated workflow will fully mirror your operational needs.
References
- Automation Rule to display epic-link on a sub-task - Atlassian
- How to sync epics stories with Jira Automation - Atlassian
- Create and Link Child Issues with Epic - Atlassian
Recommended Further Queries
Last updated February 20, 2025