Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-36467

Ability to configure/select which project page is shown by default when a Project is opened

    • 2
    • 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      A JIRA Admin would like to be able to change/configure which of the Overview sections is shown by default when a user opens a project.

      Currently, the Project Overview page remembers the section that was last viewed (e.g Overview - Summary, Overview - Issues, Overview - Agile etc.), but there is no way to configure a default landing page view for the project page.

      • This can be configurable per project or generally for all projects by Administrators.
      • This setting may also overwritten individually as a user preference option if necessary.

            [JRASERVER-36467] Ability to configure/select which project page is shown by default when a Project is opened

            This would be so nice to have

            Lasse Rørbæk added a comment - This would be so nice to have

            Comments back as far as 2020!  Are there any updates on this?

            Laura Okerstrom added a comment - Comments back as far as 2020!  Are there any updates on this?

            Not only an admin. Jira user would like to OVERRIDE what admin sets because THERE ARE MULTIPLE ROLES users have. Each role needs a different configuration. Why not to store the default view in a user cookie? Why not to store last view in the cookie. Come on, that is not that difficult to wait 8 years to figure out how many users want such simple functionality.

            Michał Czapski added a comment - Not only an admin. Jira user would like to OVERRIDE what admin sets because THERE ARE MULTIPLE ROLES users have. Each role needs a different configuration. Why not to store the default view in a user cookie? Why not to store last view in the cookie. Come on, that is not that difficult to wait 8 years to figure out how many users want such simple functionality.

            Bryan Quible added a comment - - edited

            Our use cases for this feature:

            Case #1: We are doing Alpha testing on our product. Many of the folks participating in this testing are not daily users of Jira. We have to train them how to use Jira to file any bugs they find. We want to show them the bare basics so they can get in and out of Jira as quickly as possible. 

            We want them to create their tickets in a 'special' sprint bucket where they get reviewed before being moved into the correct sprint. We think the simplest way to do this is via the Backlog view, but that means teaching them to navigate through the Active sprint view. It would be great if we could configure the preferences for these users so every time they login and navigate to the project, they go straight to the Backlog view instead of the Active sprint view.

            Case #2: Our Product Owners prefer to use the Backlog view, but every time they navigate to a different project they're forced to the Active sprint view. They want to go to the Backlog view by default where they are planning upcoming sprints. Extra clicks count against the software. On top of that, 50% of the time the Backlog view doesn't load after navigating to it form the Active sprint view.

            Bryan Quible added a comment - - edited Our use cases for this feature: Case #1: We are doing Alpha testing on our product. Many of the folks participating in this testing are not daily users of Jira. We have to train them how to use Jira to file any bugs they find. We want to show them the bare basics so they can get in and out of Jira as quickly as possible.  We want them to create their tickets in a 'special' sprint bucket where they get reviewed before being moved into the correct sprint. We think the simplest way to do this is via the Backlog view, but that means teaching them to navigate through the Active sprint view. It would be great if we could configure the preferences for these users so every time they login and navigate to the project, they go straight to the Backlog view instead of the Active sprint view. Case #2: Our Product Owners prefer to use the Backlog view, but every time they navigate to a different project they're forced to the Active sprint view. They want to go to the Backlog view by default where they are planning upcoming sprints. Extra clicks count against the software. On top of that, 50% of the time the Backlog view doesn't load after navigating to it form the Active sprint view.

            Tomasz Sip added a comment -

            What's the status?

            Tomasz Sip added a comment - What's the status?

            Sina Abdi added a comment -

            Created in 2014! Yes please, the details matter everywhere else but Atlassian it seems to be. Too many small easy enough features which improve functionality for end use are missing! And it is quite very annoying that there really is never any response from the Atlassian team! There needs to be more software engineers it seems to be!

            Sina Abdi added a comment - Created in 2014! Yes please, the details matter everywhere else but Atlassian it seems to be. Too many small easy enough features which improve functionality for end use are missing! And it is quite very annoying that there really is never any response from the Atlassian team! There needs to be more software engineers it seems to be!

            This seems like it should be a rather simple update; not sure what prevents it from being implemented.  It's basic usability – let the user choose how to configure their experience rather than force them down some preselected path that doesn't fit their need or use of the product.  

            Rhonda Gilligan added a comment - This seems like it should be a rather simple update; not sure what prevents it from being implemented.  It's basic usability – let the user choose how to configure their experience rather than force them down some preselected path that doesn't fit their need or use of the product.  

            Sina Abdi added a comment -

            FYI I can have everyone with my site access vote on this, because it is important to all of them, but I hope that is not necessary. Can some Jira support engineers comment on this and give us updates???–> Why this will or will not be updated, ask questions about it and do investigating.. Please reach out to me!

            Sina Abdi added a comment - FYI I can have everyone with my site access vote on this, because it is important to all of them, but I hope that is not necessary. Can some Jira support engineers comment on this and give us updates???–> Why this will or will not be updated, ask questions about it and do investigating.. Please reach out to me!

            Sina Abdi added a comment -

            Has this not been added, because it seems like a simple enhancement that would greatly improve the workflow and customization of the project. 

            Sina Abdi added a comment - Has this not been added, because it seems like a simple enhancement that would greatly improve the workflow and customization of the project. 

            webks GmbH added a comment -

            This would also be VERY helpful in combination with common plugins like "Structure for Jira".

            I absolutely agree with the issue descriptions suggestions.

            Thanks a lot in advance!

            webks GmbH added a comment - This would also be VERY helpful in combination with common plugins like "Structure for Jira". I absolutely agree with the issue descriptions suggestions. Thanks a lot in advance!

              Unassigned Unassigned
              takindele Taiwo Akindele (Inactive)
              Votes:
              101 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated: