Summary of Project:
We are extending the Jira Work Management list view to Jira Software projects, so customers will have a new way to view, plan and track issues within their project. This view will be accessible from the side navigation and can be toggled on/off in project settings. The list is scoped to a single project and we have no current plans to replace other lists that exist in the platform, such as the “Issues” view.
Our team is working on a tight timeline for this change and recognize it’s not ideal that we are only able to offer a short window for comments from the developer community. We are primarily focused on identifying serious flaws in our solution and any unanticipated impact to apps.
- Publish: 13 March 2024
- Discuss: 27 March 2024
Problem / Opportunity
We are adding a new task list view in Jira Software projects, to sit alongside the board, backlog and timeline. This new view will make it easier for our users to view all tasks across their Jira Software project and make quick and easy edits as they plan, groom and track their project tasks. The list view enables flexibility to roll up child issues into parents (or vice versa by drilling down into child issues), to get the level of fidelity needed at any point in time. The list view exists today in Jira Work Management Business projects and by extending this to Jira Software projects, we will be closing a feature gap between the two project types.
Proposed Solution
We will be extending the Jira Work Management list view to Jira Software projects. This view will be accessible via the side navigation, but will sit outside the board context. The list view will sit alongside other lists we have available in the platform - such as the “Issues” view. We have no current plans to merge these experiences.
The new list view includes a number of key features
- An easy to use filter: a number of quick filters will be available by default, such as Assigned to me and also filter by other specific fields such as Issue Type, Status, Label as well as Sprint and Story Points (or Story Point Estimate for team-managed projects).
- Group issues: issues can also be grouped by Status, Assignee, Priority, Story Points (or Story point estimate for team-managed projects) and Sprint (when applicable).
- Expand/collapse all issues: one of the benefits of the list view is the ability to rollup child issues into their parents, to understand the context of tasks, or drill into parents to understand the scope of work.
- Configure columns: columns can be reordered or hidden or used for sorting issues. In team-managed projects, you can also create and add a new field to your project in context, without needing to visit the configuration screen
- Toggle on/off: the view can be toggled on/off in Project Settings > Features, similar to other views today. This applied to both team-managed and company managed projects and the view will be turned on by default for all Jira Software projects.
The list view will be scoped to the Jira Software projects for now and we will consider evolving this to be scoped to the board in future iterations.
Our plan is to roll this out in April 2024.
Asks
As mentioned above, we have a short timeline for this change. Whilst we welcome feedback and suggestions on our solution, our primary asks are:
- To raise any breaking changes which we haven’t anticipated
- There are no specific APIs provided by List and no UI extension points currently available in Connect or Forge for this view. But we would love to hear your feedback on the following for future iterations to the list view:
- What APIs or UI extension points would help make your current apps better?
- What APIs or UI extension points would be useful for creating new app opportunities?
We welcome feedback and will consider this as we continue to refine the list view in Jira Software.
4 Likes
For us, it would be important to be able to:
- Add an “entry point” to our app in the context of the whole list. The entry could be:
- (most preferably) a button above the list,
- or a menu item in an “Apps” menu above the table,
- or a menu item in an “Export” menu above the template
- Our code needs to be able to get:
- the list of the columns currently selected for the list (we want to offer “Current fields” type exports)
- the list of the issues currently visible in the list sorted by the order currently used in the list (we want export the issues with those exact columns and in that exact order)
4 Likes
thanks @m.herrmann - i can see a benefit for customers in being able to do this too. Any thoughts on grouping and how you would like to interact with this feature?
We can support grouping in our apps, that could be useful, yes.
But to prioritize things, grouping would be “should have”, not “must have”. The request I mentioned in my first post are definitely “must have”.
2 Likes
Hello everyone!
First of all thanks for this RFC.
We will need to be able to position in some place in the operation toolbox with a similar location that the one that we have in the Jira issue navigator named jira.navigator.pluggable.items.
Secondly, we can manage the same use case if we are able to add an option inside the Export section if it is there.
The use case behind this is to offer an entry point for Exporter, one of Deiser main apps, that is focused on exporting issue data within the Jira issue navigator right now but it will be great to be able to be there too.
Exporter is currently developed in Connect but we are moving to Forge so having this module in both frameworks will be the best options.
Have a nice day!
1 Like
Hi @alvaro.aranda - thanks for the feedback!
Just in time for the deadline 
Like other partners, we would welcome the following features for our apps:
- support of Forge Custom Fields (rendered) in this list,
- an entry point to our app similar to the one in the Jira issue navigator (Apps->…).
- For the point above, we would like to be able to
- determine the list of columns that are currently selected and
- access the issues that are displayed there (e.g. by a JQL).
And: It would be extremely beneficial for us to have a separate entry point in both the new list location and the Issue navigator to add a summary line at the bottom of the displayed list.
This feature is currently available for Data Center, and we would appreciate it if the same could be implemented for Cloud so that we can close the feature gap between the two platforms for our app.
Now we are really excited to see what will happen in the next weeks and are waiting for the rollout!
Would it be possible to have this component available for 3rd party apps?
We currently do not support a grouping in our UI, but the lib we are using is supporting it. The issue with supporting a grouping feature would be:
The Issue search API does not support a Group By Parameter and as a result we would need to get all issues by jql and group them afterwards
1 Like
Surprisingly enough it’s already there. I swear I didn’t see last week:
1 Like
thanks for the feedback @u.masermann . Does your app support summarising input from all field types excluding text?
Hi @dmitry.astapkovich - in addition to adding in fields from your app as filter options here, is there anything else you would like to do with the basic filter component?
We are supporting all Jira number fields (system/custom) and a couple of third party fields. Actually, we are also summarizing text if it contains only numbers and option based fields like single/multiselect, checkboxes…
1 Like
Hmm… is there a basic filter component we can use in our apps? I know there’s only API to check JQL, but not a full module we can use in the app.
@LorettaBrunette , just checking if you have seen my answer.
apologies @dmitry.astapkovich . Basic mode is not available but the JQLEditor is available for Forge/Connect apps . Here is an article on this.
sorry for the delayed answer, @LorettaBrunette
basic mode would help a lot as a module. Been asking for that for years =(
thanks for the feedback @dmitry.astapkovich - I can pass this on to the relevant team (which i’m sure you have already 
)
