• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Jira Cloud for Slack
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      The "create issue from" action and /jira create commands do not currently support subtasks in Jira. Some teams may benefit from being able to create subtasks on existing issues in Slack; perhaps being able to select the parent issue if they first select subtask as the issue type.

            [API-398] Create subtasks from Slack

            jslabaugh added a comment -

            We use sub-tasks in the same way Lottie does. This feature would make for a much smoother workflow for our internal users.

            jslabaugh added a comment - We use sub-tasks in the same way Lottie does. This feature would make for a much smoother workflow for our internal users.

            Issues for us bring together all tasks relating to a specific customer.

            Sub-tasks are then the task to be completed.

            So when we get a new query from a customer, we need to be able to add it as a sub-task to the specific customers issue card.

            Currently, without this, we are unable to make use of the integration which makes Jira less useful to our team.

            Lottie Durrant added a comment - Issues for us bring together all tasks relating to a specific customer. Sub-tasks are then the task to be completed. So when we get a new query from a customer, we need to be able to add it as a sub-task to the specific customers issue card. Currently, without this, we are unable to make use of the integration which makes Jira less useful to our team.

            Is there any update on this?

            Julian Cantor added a comment - Is there any update on this?

            I agree, I do not wish to pollute an already loaded Sprint Board with a multitude of items that could simply be a list of sub-tasks under one item. 

            Derek Babin added a comment - I agree, I do not wish to pollute an already loaded Sprint Board with a multitude of items that could simply be a list of sub-tasks under one item. 

            My team tracks unplanned work originating from Slack channels ("Hey, quick question about how to deploy my new app to production...").  We create a new story every sprint for tracking unplanned work, then each unplanned request gets a sub-task under this story.  It's be great if we could just `/jira create` from the thread in Slack to create this sub-task instead of having to fumble through the Jira UI.

            Tim Gebhardt added a comment - My team tracks unplanned work originating from Slack channels ("Hey, quick question about how to deploy my new app to production...").  We create a new story every sprint for tracking unplanned work, then each unplanned request gets a sub-task under this story.  It's be great if we could just `/jira create` from the thread in Slack to create this sub-task instead of having to fumble through the Jira UI.

              Unassigned Unassigned
              deads@atlassian.com Daniel Eads
              Votes:
              51 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated: