Hi folks, Two questions: * 1 - Any method available to make the issues screen load to the "list" and not "detail" view by default? * 2 - Further on that, my end goal is to make the "view all issues and filters" (screen) for a project the default view when selecting a project. Any tips? We aren't a huge enterprise team - so it is really helpful for us to review tickets that other people are working on via the full set of header-filters, dropdowns, etc, available. Thanks for any help you can provide!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I set the issue screen to show the "list" and not "detail" view by default?

Andrew Holden

Hi folks,

Two questions:

1 - Any method available to make the issues screen load to the "list" and not "detail" view by default?
2 - Further on that, my end goal is to make the "view all issues and filters" (screen) for a project the default view when selecting a project. Any tips?

We aren't a huge enterprise team - so it is really helpful for us to review tickets that other people are working on via the full set of header-filters, dropdowns, etc, available. Thanks for any help you can provide!

Accepted answers

All comments

Chris Volker

As Admin you can set these defaults for your users. In turn this would be applied to all your projects. Users could then set their own filters as they would like. Here's a portion of the article, the link is below.

"My Defaults, Filter, and System

If the currently selected button is My Defaults, this indicates that the columns you are seeing are from your user account preferences. Filter is an available option whenever the issue search results come from a saved filter. If you are a JIRA Admin, you will also see the System tab, where you can change the columns for all users who have not set their own defaults"

Here is the link for further review:

https://confluence.atlassian.com/display/JIRA/Configuring+the+Default+Issue+Navigator

Best wishes!

Andrew Holden

Hi Chris, Thanks - but I don't (believe) this addresses my goal: The default URL for a project is something like: https://customername.atlassian.net/projects/PROJECTNAME The default issues view is something like: https://customername.atlassian.net/projects/PROJECTNAME/issues/PROJECTNAME-12?filter=allopenissues ..and features the "sidebar style" list with ticket details in the main content area. Clicking the "view all issues and filters" removes the sidebar (for me anyway) and provide the list view as a full-page-width list. https://customername.atlassian.net/issues/?jql=project%20%3D%PROJECTNAME%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC What I'm trying to do is reduce the number of steps required for any user to get to this URL after selecting a project from the top menu bar. I've seen a fair number of requests for this across the forums, etc, but the usual answer is about "columns" - which (unless I'm missing a UI control somewhere) is only a control which affects the last page and thus not relevant to the default "view" in this context. Does JIRA include controls for the default "list" layout (view-type) and starting page for a project?

Dave Neil

I'd also like to know how to do this - were you ever able to figure it out?

Andrew Holden

Hi Justin, No, I'm afraid not. Modifying the default view-type to a "list" does not seem to be an option in JIRA. Best, Andrew H.

David Wilder

I also would love to find out this answer. Any updates Andrew?

Fernanda Moreno

Two years after, I'm not sure somwone has the answer to this? I would love to know.

Stephanie Latterman

Me as well

Tim R

@Chris Volker

Thank you for your answer Chris. I think you might have misunderstood the OP's question though. I believe the OP's question is referring to the Open Issue navigator default view type.

Upon choosing a project from the Projects menu at the top of the page, you land at the Project Page, which gives you a list of items on the left side of the page. The items in the list are determined by the project type you created. For Jira project types, the first item in the list is labeled "Issues"; for Service Desk project types, the first item is labeled "Queues"; both items open your current open issues list in "Details View", which gives you a single column list of all open issues, with a section to the right of the column which shows you the details of the currently selected issue in the column.

To open the "List View", you need to click on the link in the top right corner of the "Details View" page labeled "Advanced Search".

The OP would like to make the "Issues" page default to the "Advanced Search" / "List View", rather than the current project default of "Details View". I posted screenshots of the two views on imgur.

Tl:dr

Essentially, what the OP is looking for is a way to easily navigate to a page within a project which lists the details of all issues in a table format, with a search bar for filtering issues.

I would also like to know if this is possible.

Paul V_3ji8ka

Assuming I understand and had the same problem, i.e. first time users default to "Detail" view when clicking on a filter/dashboard gadget, and we want them to see List view as we have preset the field order for them and saved with the filter

We wrote some scriptrunner code (Jira add-on) to manage exactly this from the back end, applied to all users and to changed their default view to list.

We use email as username. Script can set to list or detail (split) view as default.

import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.issue.Issueimport com.atlassian.jira.issue.IssueManagerimport com.atlassian.jira.issue.CustomFieldManagerimport com.atlassian.jira.issue.fields.CustomFieldimport java.text.SimpleDateFormat import com.atlassian.jira.issue.MutableIssueimport org.apache.log4j.Levelimport org.apache.log4j.Loggerimport com.atlassian.jira.user.UserPropertyManagerimport com.atlassian.crowd.embedded.api.Userimport com.atlassian.jira.user.ApplicationUser

CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager();
// Get current issue objectdef issueManager = ComponentAccessor.getIssueManager()
UserPropertyManager userPropertyManager = ComponentAccessor.getUserPropertyManager()
ApplicationUser user = ComponentAccessor.userManager.getUserByKey("firstname.lastname@email.com")
String propKey = "propertykey"String output;
String propValue = nullCollection col = null;
if (user != null) { // userPropertyManager.getPropertySet(user)?.setString('jira.issues.preferred.layout.key', 'split-view') userPropertyManager.getPropertySet(user)?.setString('jira.issues.preferred.layout.key', 'list-view')}

Shelli Kleman

@Paul V Curious did you create a new fragment or listener to accomplish this?

Shelli Kleman

My Listener only works on QuickSearchEvent, but I need it on the IssueSearchEvent as well.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud