Our business needs to record the progress of recurring administrative or support tasks. Is there a way to set up a Task in Jira so that it either has a recurring due date, say once a month, or spawns cases for a given period of time with default due dates?
How about this?
And if you don't want to pay for the plugin, from Jobin's post http://www.j-tricks.com/1/post/2011/05/scheduled-tasks-in-jira.html I guess you can use the same method to create issues as well.
Now there is another new add-on that 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
Let's try Repeating Issues for JIRA https://marketplace.atlassian.com/plugins/com.codedoers.jira.repeating-issues
It looks like there might be a couple of plug-ins that might satisfy your need:
If you aren't interested in fiddling with the plug-ins, you might consider creating a version called Templates that has dummy issues like the ones you have to frequently create, and then whenever you need it, clone one of them into your current iteration.
If you try any of them out and get a chance to come back here, I would be interested in which options you trialed and the reason for whatever direction you choose. I could foresee having to respond to this kind of request in the future from one of my teams and whatever you might share about your experience might inform my own future exploration and recommendation.
Will do thanks Beth. I am leaning towards the scheduler, as even though it is a bit funky, it presents a good way to see the schedule per project, but I will do some mor ework on it and update the question in a while.
It is an interesting one for me, because the business sees the ability to handle recurring tasks as a very important requirement as a client management tool.
This popped up on front page because of the spam answer but I was interested because I've written a plugin that does just this. It's internal to the company so I'm not releasing it but I can talk you through it if you want ;-)
contact me direct - firstname.lastname@example.org
Thanks everyone for the answers provided to my question. All good stuff. I am most likely going to use the scheduler mainly for simplicity. I do not really have the resources to develop custom plugins at the moment. I am probably going to put that in place early 2013.
Hi Timo, our Recurring Tasks plugin runs tasks every full hour. If you specify cron expression as "* * * * *" in your task, it still will be performed every full hour. When 'Last Run Status' shows an error like 'Field 'reporter' cannot be set. It is not on the appropriate screen, or unknown.', it means that 'reporter' field has to be added to suitable Jira Screen e.g. to 'Default Screen'. Cheers, Gebsun
Thanks...I figured that out. Now, however, when it runs I get an error: Field 'reporter' cannot be set. It is not on the appropriate screen, or unknown. Field 'assignee' cannot be set. It is not on the appropriate screen, or unknown. Both fields are filled in with known users. We really need these two fields to be filled in.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs