• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • Board - View
    • 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.

      Problem Definition

      In Jira Cloud, the Coreboards currently only allow you to see issues of standard issue types. There is no current way to force this board into showing issues that are subtasks.

      Suggested Solution

      Allow option to show subtasks on coreboards.

      Why this is important

      Users cannot see subtasks that might exist in that project when looking at this board. Since subtasks and their parent issues do not always have to have correlating statuses, it is possible that all the parent issues could be marked as completed when there are several subtasks that have not be completed. It would be helpful to be able to see these on this board.

            [JWMCLOUD-18] Coreboards should have the option to show subtasks

            This is being tracked on https://jira.atlassian.com/projects/JWMCLOUD/issues/JWMCLOUD-17 so I will close this issue - please follow JWMCLOUD-17 for updates, we have just started working on this feature

            Heather Roberts added a comment - This is being tracked on https://jira.atlassian.com/projects/JWMCLOUD/issues/JWMCLOUD-17 so I will close this issue - please follow JWMCLOUD-17 for updates, we have just started working on this feature

            +1

            Anna Ostrovska added a comment - +1

            Vote Up!

            Sven van den Heuvel added a comment - Vote Up!

            This feature is very welcome to add to the core boards! It could be a simple board config setting you can switch on an off.

            Rob Huijben added a comment - This feature is very welcome to add to the core boards! It could be a simple board config setting you can switch on an off.

            It is a must to have this as it brings so many benefits to see each task (including a sub-task) in the Board so the workload of the team can be tracked and tasks better assigned....

            Jolanta Duchowski added a comment - It is a must to have this as it brings so many benefits to see each task (including a sub-task) in the Board so the workload of the team can be tracked and tasks better assigned....

            Bastiaan added a comment -

            Looking at the timeline, I won't get my hopes up, but would be super useful, I need to see all tasks, not just mother projects. Especially in larger projects, I just need the various levels of detail. Generally, I would say sub tasks should be named differently by default... not PROJ-1 PROJ-2 etc, but PROJ-1 > PROJ-1-Sub1

            Bastiaan added a comment - Looking at the timeline, I won't get my hopes up, but would be super useful, I need to see all tasks, not just mother projects. Especially in larger projects, I just need the various levels of detail. Generally, I would say sub tasks should be named differently by default... not PROJ-1 PROJ-2 etc, but PROJ-1 > PROJ-1-Sub1

            Dominique added a comment -

            This should be a basic feature!!!! Very needed.

            Dominique added a comment - This should be a basic feature!!!! Very needed.

            This is definitely a very useful feature.

            James Bryan Gonzales added a comment - This is definitely a very useful feature.

            Rachel added a comment -

            Would find this very useful

            Rachel added a comment - Would find this very useful

            susanta added a comment -

            This is a must feature also need filters in the corebard view.

            susanta added a comment - This is a must feature also need filters in the corebard view.

              Unassigned Unassigned
              aheinzer Andy Heinzer
              Votes:
              120 Vote for this issue
              Watchers:
              42 Start watching this issue

                Created:
                Updated:
                Resolved: