How can create a monthly recurring work process with Jira?

Question

How can I use Jira to create a monthly recurring work process? Example:
a) Check invoice (me)
b) If invoice is incorrect, then send back to sender
c) If invoice is correct, then send invoice to person B for approval
d) If approval from B received, then send invoice to accounting dept.

How can I setup this process as a scheme in Jira and then run it on a monthly basis?

Trudy Claspill · Answer

If you go to the home page for this community, you should see a link for training videos above the content list.

https://community.atlassian.com/t5/Jira-Software/ct-p/jira-software

There are also tutorial videos available on YouTube.

There is also an extensive vendor documentation library.

https://support.atlassian.com/jira-software-cloud/resources/

D._4t975t · Answer

Thanks for the helpful answer, now it is clearer to me that automation is more comprehensive than workflow.

I know JIRA only as a ticket system from a previous company. However, I find it hard to get started with Jira. I don't know the difference between Jira Classic and Jira Next-Gen.

I might have to start learning about workflows. However, I can't get along with the help function at all. For example, when I type in "workflow", I get numerous search results that all look the same somehow. This puts me off a lot.
https://confluence.atlassian.com/search/?queryString=workflow

Is there a tutorial somewhere with examples? - I would like to create a workflow as described above in JIRA.

Trudy Claspill · Answer

Hello @D.

Workflows determine the different Status that a task can have, and how it can change from one status to another; i.e. To Do, In Progress, Done.

Workflows can be customized to include different statuses, to place conditions on when a task can transition from one status to another (i.e. cannot transition to In Progress unless the Assignee field has a value), to validate data as part of the transition, and to execute some functions after the transition has completed. Workflows are all based on changing the status of a task.

Automations go far beyond that. Automation can be used to create new issues, copy data between issues, set values in issues, and much more. They can be triggered by a variety of actions, not just by status transitions. The Automation setting is found under Project Settings.

Based on your question about the differences I suspect you do not have very much experience with JIRA. Is that true? Are you trying to use a JIRA Classic project or a JIRA Next-Gen project? Please provide some information about your experience level with JIRA and what, if anything, you are currently using it for, so that we can provide suggestions with enough information to provide you with meaningful help.