Create an issue with a summary to check for attachment type

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 create a sub-task with a summary to check for attachment type in the parent issue.

Configuration steps

Mode*

Choose Single issue.

Issue type*

Choose selected issue type and sub-task as its value.

Parent issue*

Choose current issue.

Summary*

Insert the following expression:

%{matches(%{issue.attachments}, ".*.txt$") ? "Text file found." : "No text file found."}

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	Workflow function	Parser functions	Complexity
Create an issue in the current project	Create issue		BEGINNER
Create an issue with a summary to check for attachment type	Create issue	matches()	INTERMEDIATE
Create a simple sub-task	Create issue		BEGINNER
Create a story in an Epic	Create issue		BEGINNER
Create a sub-task for each component	Create issue	toStringList() getMatchingValue()	BEGINNER
Create a sub-task for each user selected in a User Picker field	Create issue	jiraExpression()	BEGINNER
Create a sub-task for high priority issues	Create issue		INTERMEDIATE
Create a sub-task linked to issues with a specific priority	Create issue		INTERMEDIATE
Create a sub-task mentioning the assignee when a high priority task is ready for review	Create issue		BEGINNER
Create multiple sub-tasks with different summaries and descriptions	Create issue	nthElement()	INTERMEDIATE
Create two sub-tasks when a user story is being approved	Create issue		INTERMEDIATE

If you still have questions, feel free to refer to our support team.

Content

Space Tools

On this page