Since subtasks can't have an epic link, in turn Jira won't let you create them when in this project they are associated with a field configuration that requires it. Excluding the field from the screen won't help here either, as you already have noted. The field configuration scheme would need to be adjusted here in some manner to resolve this. With WS4J, you can create a Jira issue from Slack with an emoji, here's how: Once you have defined your project in Jira, open 'Workflow Builder' in Slack. Select 'Create’ to set up a new workflow and give it a name and select your trigger. Choose ‘Emoji reaction’ as trigger to start this workflow, then specify the Slack channel and your Open any issue in Jira. Click the "More" drop-down at the top of the screen. The convert to-subtask is not visible. Cause. There are modules in the Issue Operations Plugin that are disabled system-wide. Resolution. To resolve this issue, enable the modules that are currently disabled. Go to (Settings (cog icon on the top right) > Manage apps In the Step 1. Select Parent Issue and Sub-Task Type screen, type or select the appropriate parent issue type and the new issue type (i.e. a sub-task issue type). Select Next. If the issue's current status is not an allowed status for the new issue type, the Step 2. Select New Status screen is displayed. When a sub-task is created, I would like to copy the user specified in the parent task to the same field in the sub-task. The field is called "Projektleiter". I tried using the example in the ScriptRunner documentation but it doesn't work. Here's what I have. import static com.atlassian.jira.issue.IssueFieldConstants.*. . How to link new sub-task issue type to the (parent) issue type. I've created a project using Software Development > Scrum template which comes with standard issue types (Epic, Story, Bug, Task, Sub-Task). When navigating to the project > Project Settings > Issue Types I can see all of them in 3 groups (Epic is first group, Bug/Story/Task in Finally, when the story bug issue type is added to your issue type scheme, you will still not be able to create it directly when you hit the create button in Jira. Sub-task issue types can only be created as child issues of an issue that is at the hierarchy level above them (e.g story, bug, task). You'll need to open the parent story and choose If you’re a cloud customer and want to stop watching all server issues, open this server issue filter. On the relevant filter page, click Tools and select Bulk Change all X issue (s): Select the issues that you want to stop watching and click Next: Select Stop Watching Issues and click Next: Click Confirm to finalize any changes. Convert issues to Jira Service Management requests by adding request types. Summary. Determine what issues do not have request types. Obtain proper format for request types from the database. Add request type to affected issues using Jira Suite Utilities. The steps below will need to be performed for each request type. Detailed steps: I've created some custom fields and use these in some screens (edit, view, create). These screens are only used in project X. In project Y these custom fields are not used in any of the screens connected to the project Y. If I want to convert a sub-task to an issue in project Y, in step 3 of 4 (upda

jira convert task to bug