create a workflow and capture repetitive transaction over the year

Question

hi all, i am new to jira and a business manager.

i am trying to create a workflow with many steps and substeps. this is going to be a permanent workflow for e.g. purchase process. i want to define timelines (in days and hours, not dates) where each step/ sub step should be completed and release to team.

this will now act as a template for purchase process, where each transaction shall go through the same process and timelines by the same people.

now there are going to be hundreds of transaction every month and i want my team to update progress and follow the template and i can see everything on the dashboard to know about progress and delays for each transaction.

since every transaction shall be triggered at different times, they will have different end times.

any help is appreciated on how to create this

Zoryana Bohutska _SaaSJet_ · Answer

Hi @Abhey_Goyal

Also, you can try the solution from Atlassian marketplace - SLA Time and Report.

This add-on will let you set SLA goals according to your custom fields as start/pause/stop triggers.

Additionally, you can set time limits and automate actions for exceeded issues: notification, changing assignee, issue status or priority.

For any time you can track issues SLA and generate calculated report for issue list you need or for each issue (at the view tab).

Hope it helps

Jack Brickey · Answer

Hi Abhey, welcome to the Community and to Jira. You can certainly create a workflow that should meet your needs. If you need help getting started with workflows you might want to read this article - what-are-jira-workflows . Now regarding the part about timelines for the transitions, it sounds like some of the transitions will happen automatically after being in a status for some period of time. Assuming that is the case then you will need to rely on Automation. To learn more on this please see this article - what-are-automation-rules . On final thought, I see you are on the Free plan. Given your requirements, use case and the likely solution you may ultimately need to upgrade to standard at some point but that can wait until it is obvious.

as you move forward laying this out don’t hesitate to ask for further help.