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

Be able to query Epic assignment history of all issues ever assigned with an Epic

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.1.1
    • None
    • None
    • 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.

      COS:

      • For a given epic return the history of all issues added and removed (with time) from the Epic
      • Will need to inform admins that they need to re-index
      • This does not involve the addition of JQL to assist in this querying

      Development Notes

      Q: I'm assuming this will only be seen on the view issue page?
      A: It won't be seen in the UI anywhere. It will only be seen by accessing the URL directly.

      Q: What if the epic has been deleted?
      A: You get an error message: issue does not exist.

      Q: What if the epic was converted to an issue/subtask?
      A: It doesn't check. If you changed it in JIRA and there are still epic child links, you'll still see the data.

      Q: What if the linked issue was moved/converted/deleted?
      A: It should still show up in the appropriate group (incomplete, complete, punted)

      Q: From what version forward will we be tracking this history? aka if an epic link already existed before we introduce this change?
      A: previous epic links should be tracked

      Q: Do any of these questions surprise you? If so, what hadn't you previously considered?
      A: the first one, because it's not a UI story

      Q: What else can you think of?
      A: Not Answered

          Form Name

            [JSWSERVER-6615] Be able to query Epic assignment history of all issues ever assigned with an Epic

            Branch GHS-6615

            JoanneA (Inactive) added a comment - Branch GHS-6615

            Created a new rest URL for this report (see last comment)

            Please test by adding / removing stories from epics, change story status, different status mappings, different fields for estimation, etc.

            Does not account for changes in estimates.

            JoanneA (Inactive) added a comment - Created a new rest URL for this report (see last comment) Please test by adding / removing stories from epics, change story status, different status mappings, different fields for estimation, etc. Does not account for changes in estimates.

            The output of this story is a REST service accessed by the URL:
            http://(JIRA-URL)/rest/greenhopper/1.0/rapid/charts/epicreport/(rapid view ID)/(epic key)

            e.g. http://localhost:2990/jira/rest/greenhopper/1.0/rapid/charts/epicreport/5/FULL-5

            Tools to easily view the json
            =============================
            JSON View for Chome:
            https://chrome.google.com/webstore/detail/jsonview/chklaanhfefbnpoihckbnefhakgolnmc?hl=en

            PrettyJson for Sublime
            ======================
            https://github.com/dzhibas/SublimePrettyJson
            (v easy install)

            JoanneA (Inactive) added a comment - The output of this story is a REST service accessed by the URL: http://(JIRA-URL)/rest/greenhopper/1.0/rapid/charts/epicreport/(rapid view ID)/(epic key) e.g. http://localhost:2990/jira/rest/greenhopper/1.0/rapid/charts/epicreport/5/FULL-5 Tools to easily view the json ============================= JSON View for Chome: https://chrome.google.com/webstore/detail/jsonview/chklaanhfefbnpoihckbnefhakgolnmc?hl=en PrettyJson for Sublime ====================== https://github.com/dzhibas/SublimePrettyJson (v easy install)

            needed in order to build the table

            JoanneA (Inactive) added a comment - needed in order to build the table

              Unassigned Unassigned
              sclowes Shaun Clowes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: