I’m trying to set up a workflow in JIRA where we can group several tickets together under one main issue. Here’s what we want to do:
We have regular tasks that go through the normal development cycle (backlog, in progress, coding, etc). But then we want to create a special RFC ticket that includes all the completed work from a sprint or release.
This RFC ticket would then go through its own approval process like testing, QA review, management approval, and deployment tracking.
The question is - can JIRA automatically link a bunch of related tickets to one parent RFC issue? Or do I have to manually connect each one? I’m looking for the easiest way to group sprint items together so we can track them as a single change request through our approval workflow.
Any suggestions on the best approach for this kind of setup?
totally agree! epics are the way to go for this. just link that RFC ticket and use related or blocked labels. the bulk linking is def a time saver - makes connecting multiple tickets super easy!
JIRA’s issue linking combined with custom workflows can effectively manage this scenario. Begin by creating your RFC ticket and then utilize the “Link Issue” feature to connect it with the completed sprint items. It’s advisable to use the “blocks/is blocked by” relationships, as the RFC cannot proceed to approval until all associated tasks are finalized. For a more automated approach, establish a JQL filter based on fix version or labels to bulk link all relevant sprint tickets to your RFC in one go. If you have administrative privileges, consider leveraging automation rules that can create these links automatically when sprints conclude or ticket statuses are altered. This significantly reduces manual effort and enhances traceability between development tasks and the approval process.