Hello, this is more of a best practices question for setting up recurring tasks in Jira. I have created a project specifically for keeping track of IT scheduled tasks - most monthly, all are due a specific weekday of the nth week of the month.
I have created scheduled triggers using Cron to create them, and I would not want or expect Jira end-users to figure out how to create a recurring trigger.
For the scenario I have given, is there any straightforward way an end user could set up these types of recurring issues? I know that there is the "Set to Recur", functionality for existing tasks, but it only currently allows up to two weeks max for recurrences.
So is the rule of thumb that admins should set up triggers for these types of recurring tasks, short of getting a marketplace app that can allow the user more ability to do it themselves?
You can create automation rules on a project based on a scheduled trigger to do this.
Then a user who is granted the project admin role can create automation rules on the project.
So users with the correct rights on a project can do this via automation on the project, no cron scripts to talk to the API or 3rd party integrations are needed.
Information on automation:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Marc - My how was that users themselves could easily make a new task they create a recurring task, without the project Admin (or Jira/JSM Admin) having to do it. For us, even though the Jira projects have a person assigned as a project admin, the consensus among them is to let the project users create recurring tasks. So, it seems like no matter what, someone needs to create a scheduled trigger, and that trigger can just run as needed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.