Project

General

Profile

Actions

Feature #7459

closed

Improve ticket template

Added by L'Orphelin Cyril almost 8 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Low
Assigned To:
Frébault Pierre
Category:
Dashboard
Start date:
06/17/2014
Due date:
% Done:

100%

Estimated time:
Story points-Velocity based estimate-Release3.3Release relationshipInitial

Description

Hi,

See https://ggus.eu/index.php?mode=ticket_info&ticket_id=106149 for an example.

What does the text of the original ticket tell me?

timestamp: good
test_name: pretty much worthless
host_name: good
service: ok
status: ok, but ...

URL_to_history takes me somewhere that is potentially interesting, but the name is bad.

The ticket lacks important information; if a user submitted this ticket, I would reply with "please provide the following information". An automated system should provide better reports than a user -- the automated system presumably knows much better than a user what information is important to include.

So please ensure that in the future, the ROD-dashboard-submitted tickets includes this information. Not doing so is making a joke out of EGI -- the main function of the tool as it is now, is to save effort at the operations end. The primary function should however be to save effort for the (much larger) group of site admins, these tickets fail in this regard.

Information that should be included in the ticket.

- a link to the documentation for the SPECIFIC TEST that has failed. what is now provided is a link to a long list of tests, creating work for the admin -- she needs to find the test name and then search for it on a different page

- the exact command that failed, and the output (or lack of output) that signals that this command was not successful.

In other words, the ticket should contain enough information that I do not need to click any other links in order to understand the result and error.

An acceptable alternative is to have the page include a direct (direct means 1 single click) link to the failed test itself, showing the exact command attempted, output returned, and clear markup of the point at which failure was identified.

Thanks!

Actions #2

Updated by L'Orphelin Cyril almost 8 years ago

  • Priority changed from High to Immediate
Actions #3

Updated by Lequeux Olivier almost 8 years ago

  • Status changed from New to Assigned
  • Assigned To set to Lequeux Olivier
  • % Done changed from 0 to 50
Actions #4

Updated by L'Orphelin Cyril over 7 years ago

  • Tracker changed from Task to Feature
Actions #5

Updated by L'Orphelin Cyril over 7 years ago

  • Release set to 3.1.1
Actions #6

Updated by L'Orphelin Cyril over 7 years ago

  • Status changed from Assigned to In progress
Actions #8

Updated by L'Orphelin Cyril over 7 years ago

  • Release deleted (3.1.1)
Actions #9

Updated by L'Orphelin Cyril over 7 years ago

  • Release relationship changed from auto to initial
Actions #10

Updated by L'Orphelin Cyril over 7 years ago

  • Release set to 3.1.2
Actions #11

Updated by L'Orphelin Cyril over 7 years ago

  • Category set to Dashboard
Actions #12

Updated by L'Orphelin Cyril over 7 years ago

  • Priority changed from Immediate to Normal
Actions #13

Updated by L'Orphelin Cyril over 7 years ago

  • Priority changed from Normal to Urgent
Actions #14

Updated by L'Orphelin Cyril over 7 years ago

  • Priority changed from Urgent to Low
Actions #15

Updated by L'Orphelin Cyril over 7 years ago

  • Release deleted (3.1.2)
Actions #16

Updated by L'Orphelin Cyril over 6 years ago

  • Target version set to next
Actions #17

Updated by L'Orphelin Cyril over 6 years ago

  • Release set to 3.3
Actions #18

Updated by Frébault Pierre over 6 years ago

  • Target version deleted (next)
Actions #19

Updated by Frébault Pierre over 6 years ago

  • Assigned To changed from Lequeux Olivier to Frébault Pierre
Actions #20

Updated by Frébault Pierre over 6 years ago

  • Status changed from In progress to Resolved
  • % Done changed from 50 to 100
Actions

Also available in: Atom PDF