| Table of Contents |
|---|
...
| Info | ||
|---|---|---|
| ||
Power Scripts Scripts™ for Jira (server) Level: BASIC |
...
Solution
One will need to add a SIL SIL™ condition on the close transition which will verify the statuses of all dependencies (child and linked issues). If any of the dependencies is not already closed the condition will return false.
...
For the sake of this exercise we will consider that all subtasks need to be closed in order to let an issue to be closed.
Add a new condition
Log in as an administrator and navigate to Administration-> Workflows and edit "Close Issue" transition on your Jira workflow.
Press "Add a new condition" link.
Select (k) SIL SIL™ Condition and then press Add.
Writing the
...
SIL™ code
The page Add Parameters To Condition apprearsappears. In the SIL SIL™ code edit area insert the following code:
...
| Info | ||
|---|---|---|
| ||
All you have to do now is to publish your workflow. See more at Activating Workflow section on Atlassian Documentation. |
See also
- Restrict workflow based on status of dependenciesDisabling inline edits in Jira
- Forbidding users to create some issue types
- Hide fields from users not in a project role
- Limit Number of Characters in Text Field
- Lock an issue - a better variant (Live Fields)
- Locking Issues
- Making an issue read-only
- Require User to Log Work Before Transitioning Issue
- Restrict issue type availability by user
- Restrict workflow based on status of dependencies
- Validator for component lead