Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-6073

Improve the "Create a New BF JIRA Ticket" workflow

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Notifications
    • Labels:
      None

      Description

      I find the "Create a New BF JIRA Ticket" workflow in Evergreen somewhat difficult to use. Clicking the "FILE TICKET" button produces a message saying "Ticket successfully queued for creation" and then it is up to me to find that ticket.

      From that point onward it is never clear to me - do I search by the task name, by the test name or by something else, so I end up refreshing the Evergreen tab, hoping that the ticket will show up there. This is problematic if there are already other tickets filed against that task/test, because they also show up.

      What would be helpful is if Evergreen kept refreshing until it has the ticket number, or alternatively if the "Ticket successfully queued for creation" message contained at least a Jira query link so I can try to find it myself.

      The reason why this is annoying is because sometimes I look at failure in a patch build and I have this grand revelation about what is causing the BF and want to quickly note it down in the ticket for whoever picks it up. With the current workflow, by the time I get to start writing in the BF description, my mental capacity has instead been shifted to locating the BF

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                backlog-server-evg Backlog - Evergreen Team
                Reporter:
                kaloian.manassiev Kaloian Manassiev
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: