Steps to Reproduce:

      1. Install JIRA
      2. Access JIRA using the url http://<servername>:<portnumber>/<context>

      Expected Results:

      The Dashboard URL is open (as in JIRA 5.0) /secure/Dashboard.jspa

      Actual Results:

      This redirects to /login.jsp?os_destination=%2Fsecure%2FDashboard.jspa

      Associated Information (When applicable):

      Accessing the URL /secure/Dashboard.jspa opens the Dashboard page

            [JRASERVER-34216] Accessing Base Url Leads to Login Page

            Eric Dalgliesh added a comment - Branch builds https://jira-bamboo.internal.atlassian.com/browse/JIRASIXSTABLE-UNIT6 https://jira-bamboo.internal.atlassian.com/browse/JIRASIXSTABLE-WEBDRIVER40 https://jira-bamboo.internal.atlassian.com/browse/JIRASIXSTABLE-CIFUNCHAL2

            On branch stable-JRA-34216

            Eric Dalgliesh added a comment - On branch stable- JRA-34216

            OK, let's fix this, but make it BTF-only.

            Eric Dalgliesh added a comment - OK, let's fix this, but make it BTF-only.

            For clarification of the new behaviour - we now redirect to the login page if there are no anonymous-viewable projects.

            We made a decision to do this in order to improve the login flow, as we thought the Dashboard would not be useful if there are no Projects that are viewable by anonymous users - they would have to login in order to view content.

            It appears that this has broken the login flow for this particular BTF instance, in which case we should revisit our original decision and at least offer some form of work-around.

            ig (Inactive) added a comment - For clarification of the new behaviour - we now redirect to the login page if there are no anonymous-viewable projects. We made a decision to do this in order to improve the login flow, as we thought the Dashboard would not be useful if there are no Projects that are viewable by anonymous users - they would have to login in order to view content. It appears that this has broken the login flow for this particular BTF instance, in which case we should revisit our original decision and at least offer some form of work-around.

            RenjithA added a comment - - edited

            Eric,
            That JRADEV is meant for OnDemand, BTF should have be retained the same way

            RenjithA added a comment - - edited Eric, That JRADEV is meant for OnDemand, BTF should have be retained the same way

            This makes no sense to me. Furthermore, how do I get the original way back? Why do you have the introduction option in the general settings if you are not going to show it?

            Timo Jansen added a comment - This makes no sense to me. Furthermore, how do I get the original way back? Why do you have the introduction option in the general settings if you are not going to show it?

            Eric Dalgliesh added a comment - - edited

            The original issue is at https://jdog.atlassian.net/browse/JRADEV-20362 - it's not publicly viewable though

            Eric Dalgliesh added a comment - - edited The original issue is at https://jdog.atlassian.net/browse/JRADEV-20362 - it's not publicly viewable though

            This was a deliberate change. Anonymous users can still access the dashboard by going to it directly.

            Eric Dalgliesh added a comment - This was a deliberate change. Anonymous users can still access the dashboard by going to it directly.

            As the system dashboard contains important information for our users, we do not consider this a minor issue.

            Timo Jansen added a comment - As the system dashboard contains important information for our users, we do not consider this a minor issue.

              edalgliesh Eric Dalgliesh
              rpillai RenjithA
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: