Page History
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
On this page
|
UI Text Box | |||||||
---|---|---|---|---|---|---|---|
| |||||||
Use caseTransition the parent issue to another issue | |||||||
Page properties | |||||||
| |||||||
Function | <link to function being used> | ||||||
Type | post function | ||||||
Use case description | Transition the parent issue to another issue | ||||||
Complexity |
| ||||||
In Jira you can easily structure your work by using different issue types. And also sub-tasks! Once all sub-tasks are completed, the parent issue can also be marked as completed. But what if one sub-task gets reopened? In this use case the parent issue is automatically reopened, if one sub-tasks is reopened, too. In the following use case we show you how to do it! |
Configuration
UI Steps | |||||||
---|---|---|---|---|---|---|---|
|
Basic configuration*
|
After checking if the parameters match this example, you can click on add and this is how the post function should look like.
Now that you are familiar with this post function and what it does, you can configure the parameters based on your needs.
|
Screenshots
Related examples
Page properties report firstcolumn Use case headings TypeJWT feature, Function, Use case description, ComplexityWorkflow function, Parser functions, Label sortBy Title cql label = "use-case-workflow" and space ancestor = "JWTSDC27067064"
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Page properties | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|
Page properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|