Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
bgColor#f5f5f5
titleColor#ffffff
borderWidth0
titleBGColor#000000
title

...

Looking for Jira

...

Server/Data Center?

This is the documentation of JSU for Jira Cloud. If you are using JSU on Jira Server

...

/Data Center, you can find the documentation here.

(tick) Optimize your approval processes based on your team's needs: Budget approval, Travel approval, Production approval, etc.

Do you often set up issues that need approval to move to production? Do you need budget approval from your manager only for large budgets but not for smaller ones? In every organization, a budget approval process is required. Trigger budget approval efficiently and in accordance with your company's policies and rules with JSU. 

With JSU Automation Suite for Jira Workflows you can configure, that the workflow will transition automatically to the correct status. 

Have a look at the diagram below.

Image Removed

After the user submits the budget, JSU will continue from the DECISION status and automatically forward the process to the correct status, depending on the business rules in place: here, Budget <= 1'000 OR Budget > 1'000.

Check out the "How to" video further below to configure your budget approval automation.

How to configure this workflow

...

Watch this video to see all of this in action:

Widget Connector
width600
urlhttps://www.youtube.com/watch?v=tUzCfEBXfRk
height350

...



Info

NOTE: This guide starts from the "Edit Workflow" screen of a chosen project. If you're not sure how to get to this page, follow the onboarding steps first on either: Edit the workflow of a new project or Edit the workflow of an existing project


(tick) Save you and your users' time and effort by letting JSU streamline approvals in your workflow


↓ Follow the visual step-by-step guide below to see how to configure this automation in your Jira instance. ↓


  1. If you use Jira to manage approvals in a workflow, then you'll know how any unnecessary steps and actions can cause frustration for those requesting approval, and those approving too.

    Below is an example "approvals workflow" that is already configured as part of this tutorial. If you want, you can re-create this workflow in your instance in a few minutes. The main feature of the workflow is that from the 
    Status
    colourBlue
    titlesubmit
     status, the issue could then move to either 
    Status
    colourBlue
    titleawaiting approval
     or 
    Status
    colourBlue
    titleapproved
    . We'll add the logic to automate this decision-making in future steps.

    Image Added

  2. To begin automating this workflow, we first want to set the criteria we'll use for determining what "requires approval" and what can be streamlined to be automatically "approved".

    For our example workflow, we want to require approval for issues where the field "Budget Required" is over 1000. Where it is less than 1000, we'll let JSU automatically approve the request for us. To get started, make sure you're in "Edit Mode" for your workflow and then click on the transition (arrow) connecting the  
    Status
    colourBlue
    titlesubmit
     and 
    Status
    colourBlue
    titleAWAITing approval
     statuses.

    Image Added

  3. From the pop-up that appears - click on "Conditions".

    Image Added

  4. Now let's choose "Add Condition".

    Image Added

  5. From the list of Conditions, choose "Value Field" and then click "Add".

    Image Added

  6. Now, let's configure the Condition to ensure only the issues we desire have the ability to transition to 
    Status
    colourBlue
    titleawaiting approval
    .

    Field - Choose the field you want to inspect the value of, to determine whether an approval can be streamlined for it. In our case, we have a field called "Budget Required" that we've chosen.

    Condition - Choose the type of comparison you're going to use when comparing with the value. In our case, we want to require approval when the "Budget Required" is greater than (or equal to) 1000. So we need to choose "greater-than-or-equal-to / >="

    Value - Type in the value you want to compare the Field against. In our example, our chosen value is "1000".

    Comparison Type - To ensure the Value (a number) can be compared against the Field (also a number), we need to specifically tell Jira that in this scenario that Value is a "Number".

    When you're happy with the configuration, click "Add".

    Image Added

  7. You will now see a preview of the Condition we've just configured.

    Image Added
  8. You will be presented with a “Publish Draft Workflow” pop-up. It's not necessary to save a draft. Click "Publish" when you're happy and then we'll move on to the next transition.

    Image Added

  9. Head back your approvals workflow in Edit Mode. Now let's select the transition (arrow) connecting 
    Status
    colourBlue
    titlesubmit
     and 
    Status
    colourBlue
    titleapproved
     and again click "Conditions" in the pop-up that appears.

    Image Added

  10. Repeat Steps #4 - #6 to configure the "Value Field" Condition against this transition. The only difference with the configuration here is that we're going to set the "Condition" to "less-than / <" to ensure that issues with a "Budget Required" of less than 1000 can be moved next to 
    Status
    colourBlue
    titleApproved
     instead of 
    Status
    colourBlue
    titleawaiting approval
    .


    Image Added

  11. After this, and just like in Steps #5 - #8, now you will need to "Add" the Condition, and then publish the draft workflow to make it active.

  12. Almost there! Now it's time to add our automation to let JSU make this approval decision for us, based on the "Budget Required" values when users move their issues to the 
    Status
    colourBlue
    titlesubmit
     status.

    Head back to your approvals workflow in Edit Mode. Now let's select the transition (arrow) connecting 
    Status
    colourBlue
    titleIn progress
     and 
    Status
    colourBlue
    titlesubmit
    , but this time select "Post-Functions" in the pop-up that appears.


    Image Added

  13. Click "Add Post Function" towards the right-hand side of the screen.

    Image Added

  14. From the list of Post-Functions, choose "Follow Up Transition (JSU)", then click "Add".

    Image Added

  15. There's nothing you need to configure on the next screen, so all you need to do is click "Add".

    Image Added

  16. Just like before, don't forget to Publish the workflow to make this new automation active.

    Image Added

  17. Now let's go see the workflow in action!

    Head to an open issue in your Approvals project. In our case, we have an issue currently in  
    Status
    colourBlue
    titleIn progress
     and with a "Budget Required" of 500.

    Image Added
  18. Now, let's move the status to 
    Status
    colourBlue
    titlesubmit
     and watch the magic happen!

    Image Added
  19. Watch the issue move to the 
    Status
    colourBlue
    titlesubmit
     status, but then a second (or two) later move automatically to the 
    Status
    colourBlue
    titleapproved
     status!

    Image Added

  20. HINT: The issue history confirms this streamlined transition did in fact happen!

    Image Added

  21. Now try the same scenario, but where the "Budget Required" is 1000 or more.

    Image Added
  22. Let's move this issue to 
    Status
    colourBlue
    titlesubmit
     just like we did before.

    Image Added
  23. Again, the issue will be forwarded onto its appropriate next transition, in this case as the "Budget Required" is greater-than-or-equal-to 1000, it's moved next to 
    Status
    colourBlue
    titleawaiting approval
    !

    Image Added
  24. Once again, the issue history confirms to us it was JSU helping us streamline the approvals here.

    Image Added

  25. There you have it! Streamlining your approval processes in Jira just got a lot easier thanks to the power of JSU (star)


Need more information or help? Get in touch!