We are currently using a JIRA project for Issues that will need to be repeated in the future, e.g. a task to manually collect data will need to be repeated on a monthly, quarterly, or annual basis. We are wondering how best to use JIRA for the purpose of planning the repetition of those issues.
The goals we have are:
1. Reduce duplicating information; re-use or easily reference the original Issue
2. Plan (have visibility into) the future work so we can have resources properly allocated
Issue 1 to manually collect ABC info, took 3 days to complete - need to repeat on quarterly basis
Issue 2 to manually collect XYZ info, took 2 weeks to complete - need to repeat on annual basis
Would it be best to create a sub-task of the original Issue, or clone the original Issue?
From a planning perspective, should we use Greenhopper?
For example, could we use a board that has sprints labeled "Monthly", "Quarterly" and "Annually"? I didn't think this would be possible since my impression is that sprints are sequential end-to-end, e.g. Sprint 1 has to be completed before you can start Sprint 2. If that is correct, could swimlanes be used to group "Monthly", "Quarterly" and "Annually" Issues?
Any pointers for how to plan for repetitive issues would be much appreciated!
you can try Repeating Issues for JIRA https://marketplace.atlassian.com/plugins/com.codedoers.jira.repeating-issues
With this add-on you can create recurring issues and more. You can select different actions to execute repeatedly for given issue e.g. clone issue, create sub-task in issue, reopen issue
Take a look at this addon:
You can also try using a Jelly Script Service:
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot