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

Show the same information for linked issues and subtasks (e.g. status text, issue key)

XMLWordPrintable

    • 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.

      Please see attached screenshot.

      When looking at an issue, the following columns are shown for sub-tasks:
      Number | Summary | Issue Type Icon | Status Icon | Status Text | Assignee

      but for linked issues the following columns are shown:
      Link Type | Issue Type Icon | Issue Key | Summary | Priority Icon | Status Icon

      Especially the missing 'Status Text' for linked issues is giving us a lot of trouble, because it is difficult to assess the status of e.g. blocking issues. We believe this should be homogenized because sub-tasks are also just (internally) linked issues.

      If there is a way of customizing the behavior through the configuration, please point me to it. I still believe it is a valid improvement request and the current behavior needs to be changed.

      Thanks!

        1. jira_issue_subtask_links_columns.png
          jira_issue_subtask_links_columns.png
          30 kB

            [JRASERVER-29407] Show the same information for linked issues and subtasks (e.g. status text, issue key)

            Kerrod Williams (Inactive) added a comment -

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            Fabian Meier added a comment -

            It's all in a Map<String,Object> returned by com.atlassian.jira.plugin.viewissue.issuelink.IssueLinkContext.getMap() and rendered via atlassian-bundled-plugins\jira-view-issue-plugin-5.1.5\issuelink\localissuelink.vm

            God knows what's in that map (they are not even using the standard names: e.g. summary is contextMap.title) thus we cannot customize it

            Fabian Meier added a comment - It's all in a Map<String,Object> returned by com.atlassian.jira.plugin.viewissue.issuelink.IssueLinkContext.getMap() and rendered via atlassian-bundled-plugins\jira-view-issue-plugin-5.1.5\issuelink\localissuelink.vm God knows what's in that map (they are not even using the standard names: e.g. summary is contextMap.title) thus we cannot customize it

              Unassigned Unassigned
              4ef8826114c9 Fabian Meier
              Votes:
              6 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: