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

Users and Roles screen renders invalid link in React mode resulting in 404 error

XMLWordPrintable

      Issue Summary

      Users and Roles screen in the project settings will render invalid link in React mode (default since 8.60). The link rendered for users is always like this:

      <base url>/jira/secure/ViewProfile.jpsa?name=<user>

      The jira part of URL is invalid, since the base URL is set to something like <base URL>/myjiraserver/ and the link should respect that. Note that when the base URL does not have any URL suffix, the jira part is still rendered, though when clicked you can still get where you want, but if you have a context path specified in your jira, you will get HTTP 404 error.

      Steps to Reproduce

      1. Go to any project settings -> Users and Roles
      2. Add any user to the table and check the link rendered for it.

      Expected Results

      The link rendered should respect the context path.

      Actual Results

      Context path rendered always as jira, if clicked you might get 404 if your Jira is using a different context path.

      Workaround

      As a temporary workaround, you can disable rendering of that screen through React and revert to the previous way of rendering:

      • Navigate to the following page to access the Dark Features page: 
        <baseUrl>/secure/admin/SiteDarkFeatures!Default.jspa
      • Enter jira.users.and.roles.page.in.react.disabled in the field “Enable dark feature” and clicking on the “Add” button, and verify that the dark feature jira.users.and.roles.page.in.react.disabled is showing in the table.

            [JRASERVER-71573] Users and Roles screen renders invalid link in React mode resulting in 404 error

            Frank added a comment -

            Affects most of our users, since we have 5 productive Instances of Jira running and only 2 are effected (so far). As many of our users use more than one instance, they have different user experience on the different systems. So we have a few thousand users having this problem.

            Implementing the workaround on all instances to have the same UI experience isn't an option.

            Frank added a comment - Affects most of our users, since we have 5 productive Instances of Jira running and only 2 are effected (so far). As many of our users use more than one instance, they have different user experience on the different systems. So we have a few thousand users having this problem. Implementing the workaround on all instances to have the same UI experience isn't an option.

            Divya TV added a comment -

            This affects our 25,000 user community and we are on version 8.13.12

            Divya TV added a comment - This affects our 25,000 user community and we are on version 8.13.12

            David Chan added a comment -

            https://getsupport.atlassian.com/browse/PS-86012

            David Chan added a comment - https://getsupport.atlassian.com/browse/PS-86012

            Matthias Krauss added a comment -

            Observed on Jira 8.12.1

            Matthias Krauss added a comment - Observed on Jira 8.12.1

              Unassigned Unassigned
              apatyuchenko Andrey Patyuchenko
              Affected customers:
              15 This affects my team
              Watchers:
              25 Start watching this issue

                Created:
                Updated: