Every quarter the operations team has to do the same set of tasks, let's just say patching UNIX servers.
I know I cannot clone the current task because it clones all information, including the Fix Version/s, Sprint, etc.
I didn't know if there was a consensus on how people have handled it. I see the add-on Recurring Tasks for JIRA (Cloud) and Repeating Issues (Server) as two options to automate this process. I am not asking a Cost/Benefit analysis for the add-ons, I am wondering if others have found it easier to just manually enter these repeated quarterly tasks as opposed to finding an automated solution.
Personally, it seems like an automated solution makes sense if the items are exactly the same and repeated monthly, but this is the first time I've had to work with an Enterprise Infrastructure Team using JIRA.
Hi @Stephen Costanzo ,
I typically set up a table on a Confluence page and use the Jira macro to create an issue for each of the table rows. This keeps the set of tasks well documented and visible plus easily creates a new set of issues every time I need them. Cheers!
Here's the latest documentation on the Jira Issue Macro:
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events