Panel | |
---|---|
bgColor | #f5f5f5 |
titleColor | #ffffff |
borderWidth | 0 |
titleBGColor | #000000 | title | JSU for Jira Cloud
Info | |
This is the documentation of for JSU for Jira Cloud. If you are using JSU on Jira Server or on Jira Data Center, you can find the documentation heresee this use case in the Server/Data Center documentation. |
...
Preconditions allow you to execute a post function only under certain circumstances only. This helps you create a more complex behaviour behaviors on your post functions, enabling you Jira to let Jira perform do more work for you. In JSU Cloud, preconditions are not separate post functions, but part of the post functions. Now you select your preconditions on the post function configuration screen.
Check out a very common The following use case , and explains how to get started with JSU preconditions for post - functions.Every organisation employs
Goal | Automate your budget approval issues |
...
Scenario | You want to organize your budget approval issues |
...
using a project component. We will use the |
...
Update Any Issue Field post function to set the issue component to Budget, ONLY IF:
|
...
|
...
|
...
|
...
Let's |
...
have a look at how this can be automated using preconditions with JSU. | |
Components |
How to configure this rule
Create a draft of your project workflow. If you're unsure how to get to this page, follow the onboarding steps in Edit a Jira Workflow. You can then view your workflow in Text or Diagram mode. The steps in this use case represent Diagram mode. If you haven't already, switch the workflow viewer to Diagram mode.
We want our automation to be executed on the
...
Create
...
transition, so we select the
...
2. Configure the preconditions
...
arrow that points to
to display the Options menu.Status title To Do Select Post Functions then select Add Post Function to display the list of available post functions.
Select the Update Any Issue Field (JSU) post function then select Add at the bottom of the page.
On the post function configuration page, select Add Precondition.
We want our preconditions to ensure that only issues with issue type
...
, Story
...
and
...
a Summary containing
...
budget
...
text should be targeted for our post function execution.
...
Add the
...
...
precondition, and set
Issue Type = Story
Add the JQL precondition, and define a query to ensure that only issues containing
...
budget
...
in their summary will be found
...
e.g.
key={issue.key} AND summary~budget
.
You can configure the above
...
preconditions using only
...
JQL. In this case, the search query would be:
key={issue.key} AND summary~budget AND issuetype=
...
Story
. Use a configuration method that is simplest for you.
...
Always
...
include the query
key={issue.key}
...
(or similar) on your JQL condition. This
...
ensures that JQL is performed on the current issue. For more details see
...
...
...
Configure the
...
- Then, we continue with the execution by configuring our post function to add a component "Budget" to our issues satisfying the preconditions.
- Finally we save the configuration of the post function and publish our workflow.
4. See it in action!
...
post function.
Preconditions must be: set this to True.
Update field on all issues related as: select Within same issue.
Issue Field: select Component.
Field Value: enter
Budget
.
Select Add at the bottom of the page.
Publish the workflow.
Test the rule
To test our rule, we create an issue with issue type
...
Story
...
and call it
...
Budget for Hardware
...
.
...
When
...
we reload the issue, we can see that JSU
...
updated it with the component
...
Budget
...
.
...
Demo Video
Watch the demo below to follow all the steps to get your preconditions work for your post functions.Need more Information view this rule in action.
Widget Connector | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
Need more information or help? Check out the JSU documentation on topic for preconditions for post functions or Get get in touch!
Demo Video
Watch this video to see all of this in action: