On this page
Use case
Creating many issues and adding a summary and a description can be a bit frustrating and time-consuming.
To avoid such things, the following use case shows you how to do it.
Configuration steps
Issue type*
Choose selected issue type and sub-task as its value.
Parent issue*
Choose current issue.
Summary*
Insert the following expression:
getMatchingValue({seed.number},[1],
["Documentation"])
With parsing mode set to general.
Description
Insert the following expression:
getMatchingValue({seed.number},[1],
["Issue for creating the documentation for the feature"])
With parsing mode set to general.
Run as*
Choose which user* will be able to execute the post function. By default, it is set to the Current user.You use these steps the same way for creating other issues for updating the marketplace presence for the app, for creating a newsletter for features, and much more.
Related examples
| Use case | Type | Function | Use case description | Complexity |
|---|---|---|---|---|
| Create an issue in the current project | Create an issue in the current project and additionally set a summary. This use case comes in handy if you quickly need to create i.e. a new bug which relates to the current issue | BEGINNER | ||
| Create an issue with a summary to check for attachment type | Creating many issues and adding a summary and a description can be a bit frustrating and time-consuming. To avoid such things, the following use case shows you how to create a sub-task with a summary to check for attachment type in the parent issue. | INTERMEDIATE | ||
| Create a simple sub-task | Create a sub-task, set the summary based on the parent's component, and set the assignee to the current user. | BEGINNER | ||
| Create a story in an Epic | Link your Epic each time you create a story. | BEGINNER | ||
| Create a sub-task for each component | Create a sub-task for each selected component in the current issue. | BEGINNER | ||
| Create a sub-task for each user selected in a User Picker field | Create automatically a sub-task for each selected user in a User Picker (multiple users) field of the transitioned issue. | BEGINNER | ||
| Create a sub-task for high priority issues | Create a sub-task only if the priority of the current issue is "High". | INTERMEDIATE | ||
| Create a sub-task linked to issues with a specific priority | Create sub-tasks and link them to the parent or current issue that has a specific priority of your choice. | INTERMEDIATE | ||
| Create a sub-task mentioning the assignee when a high priority task is ready for review | Keep your team on track and up to date by creating a sub-task mentioning the assignee's full name and with issue links linked to the appropriate issue whenever a high priority issue has been moved to the status "Review" | BEGINNER | ||
| Create multiple sub-tasks with different summaries and descriptions | Create multiple sub-tasks with different summaries and descriptions. | INTERMEDIATE | ||
| Create two sub-tasks when a user story is being approved | When a story is approved, two sub-tasks for Development and QA will be created. | INTERMEDIATE |
If you still have questions, feel free to refer to our support team.
