Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-7116

JQL custom field names must not be hardcoded

This issue is archived. You can view it, but you can't modify it. Learn more

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest (View bug fix roadmap)
    • 6.1.2
    • None
    • None
    • None

      Javascript uses "Issue Count" as well as "Epic Link" literals in the code, yet these should come from the server as both are translatable

          Form Name

            [JSWSERVER-7116] JQL custom field names must not be hardcoded

            It looks pretty much ok for me - I've changed the names and looked at the generated JQL and it seems correct.

            Nikolay Petrov (Inactive) added a comment - It looks pretty much ok for me - I've changed the names and looked at the generated JQL and it seems correct.

            Committed on default.

            The fix here is to use the field ID instead of name, because that always works. EXCEPT, it doesn't work when the field is a custom field, which is not applicable to all issues types.

            So when the estimation statistic is a custom field, the Unestimated Incomplete query will fall back to issue keys instead of something smarter.

            Michael Tokar added a comment - Committed on default. The fix here is to use the field ID instead of name, because that always works. EXCEPT, it doesn't work when the field is a custom field, which is not applicable to all issues types. So when the estimation statistic is a custom field, the Unestimated Incomplete query will fall back to issue keys instead of something smarter.

            This breaks when estimate statistic is "Original Time Estimate". The reason is that there is no field called "Original Time Estimate".

            Rather than using the estimate name in the JQL string, we should use the field id property.

            Michael Tokar added a comment - This breaks when estimate statistic is "Original Time Estimate". The reason is that there is no field called "Original Time Estimate". Rather than using the estimate name in the JQL string, we should use the field id property.

            on default

            QA:

            • Changed epic link custom field name to random value
            • Go to epic report and click "view in navigator"
            • JQL query should be using correct custom field name
            • Configure baord to use Issue Count as estimation
            • Verify epic report behavior is same

            MichaelA (Inactive) added a comment - on default QA: Changed epic link custom field name to random value Go to epic report and click "view in navigator" JQL query should be using correct custom field name Configure baord to use Issue Count as estimation Verify epic report behavior is same

            Epic Link
            Issue Count

            Michael Ruflin (Inactive) added a comment - Epic Link Issue Count

              Unassigned Unassigned
              miruflin Michael Ruflin (Inactive)
              Archiver:
              mandreacchio Michael Andreacchio

                Created:
                Updated:
                Resolved:
                Archived: