We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-1949

[JIRAALIGN-1949] Status Reports does not reflect platform terminology change

    • 1
    • Severity 3 - Minor
    • Rockets - Usher 1

      Issue Summary

      Status Reports does not reflect platform terminology change

      • This has been tested and confirmed for "Driver"
      • Other terminology may have same problem
        • If you experience this with other terminology please let us know by commenting on this bug

      Steps to Reproduce

      1. Customize terminology for "Driver" field
      2. Navigate to Status Report - Use "Status" view
        • Click "View Status" in upper right if the button appears.
        • The report with problem is the "Status" report, not "Financials" report. URL will contain "FINSHO=2" when looking at the report with the problem
      3. Open Extra Configs menu and select "Yes" next to "Driver"
        • Note it says Driver, does not reflect custom terminology
      4. View "Driver" column now that it shows in report
        • Note it says Driver, does not reflect custom terminology. Also hover over column name, note tooltip does not reflect custom terminology

      Expected Results

      Custom terminology appears in all places

      Actual Results

      Custom terminology not reflected in Status Report

      Workaround

      No workaround is available

        1. screenshot-1.png
          screenshot-1.png
          552 kB
        2. screenshot-2.png
          screenshot-2.png
          132 kB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Align'
            1. Jira Align
            2. JIRAALIGN-1949

            [JIRAALIGN-1949] Status Reports does not reflect platform terminology change

              • 1
              • Severity 3 - Minor
              • Rockets - Usher 1

                Issue Summary

                Status Reports does not reflect platform terminology change

                • This has been tested and confirmed for "Driver"
                • Other terminology may have same problem
                  • If you experience this with other terminology please let us know by commenting on this bug

                Steps to Reproduce

                1. Customize terminology for "Driver" field
                2. Navigate to Status Report - Use "Status" view
                  • Click "View Status" in upper right if the button appears.
                  • The report with problem is the "Status" report, not "Financials" report. URL will contain "FINSHO=2" when looking at the report with the problem
                3. Open Extra Configs menu and select "Yes" next to "Driver"
                  • Note it says Driver, does not reflect custom terminology
                4. View "Driver" column now that it shows in report
                  • Note it says Driver, does not reflect custom terminology. Also hover over column name, note tooltip does not reflect custom terminology

                Expected Results

                Custom terminology appears in all places

                Actual Results

                Custom terminology not reflected in Status Report

                Workaround

                No workaround is available

                  1. screenshot-1.png
                    screenshot-1.png
                    552 kB
                  2. screenshot-2.png
                    screenshot-2.png
                    132 kB

                        kforeman@atlassian.com Kyle Foreman
                        tevans Tim Evans (Inactive)
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            kforeman@atlassian.com Kyle Foreman
                            tevans Tim Evans (Inactive)
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: