Difference between revisions of "Track User Support Requirements"
Line 16: | Line 16: | ||
| Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: only 1 reply received so far: https://rt.egi.eu/rt/Ticket/Display.html?id=704<br> | | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: only 1 reply received so far: https://rt.egi.eu/rt/Ticket/Display.html?id=704<br> | ||
Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | ||
1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". | |||
|- | |- | ||
|2.Better (more verbose and informative) error messages | |2.Better (more verbose and informative) error messages | ||
Line 22: | Line 23: | ||
| Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet.<br> | | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet.<br> | ||
Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | ||
1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". | |||
|- | |- | ||
|3.Fixing the known bugs before adding new features | |3.Fixing the known bugs before adding new features | ||
Line 28: | Line 30: | ||
| Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet.<br> | | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet.<br> | ||
Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | ||
1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". | |||
|- | |- | ||
|4.Coherency of command line commands, parameters and APIs | |4.Coherency of command line commands, parameters and APIs | ||
Line 35: | Line 38: | ||
| Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet.<br> | | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet.<br> | ||
Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | ||
1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". | |||
<!--- | <!--- | ||
[https://rt.egi.eu/rt/Ticket/Display.html?id=681 #681 (split) -> 1149] | [https://rt.egi.eu/rt/Ticket/Display.html?id=681 #681 (split) -> 1149] | ||
Line 45: | Line 49: | ||
| Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet.<br> | | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet.<br> | ||
Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | Feb 2011: UCST invited the providers of reusable tools to comment on the requirement | ||
1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". | |||
|- | |- | ||
|} | |} |
Revision as of 14:46, 1 April 2011
Main | Submit | Track |
UMD (TCB) | Operations (OMB) | User Support (UCB) |
Status at UCB
Name of the topic | Related requirements | Date when has been flagged as priotiry topic by the UBC | Current status |
---|---|---|---|
1.Increased stability and scalability for gLite WMS | Extension:RSS -- Error: "https://service-requirements:Teoer02i@rt.egi.eu/requirements/Search/Results.rdf?Order=DESC&OrderBy=Created&Query=Queue%20%3D%20'requirements'%20AND%20'CF.{Custom%20Tag}'%20%3D%20'ucb1'" is not in the list of allowed feeds. There are no allowed feed URLs in the list. | 30 Nov 2010 | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: only 1 reply received so far: https://rt.egi.eu/rt/Ticket/Display.html?id=704 Feb 2011: UCST invited the providers of reusable tools to comment on the requirement 1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". |
2.Better (more verbose and informative) error messages | Extension:RSS -- Error: "https://service-requirements:Teoer02i@rt.egi.eu/requirements/Search/Results.rdf?Order=DESC&OrderBy=Created&Query=Queue%20%3D%20'requirements'%20AND%20'CF.{Custom%20Tag}'%20%3D%20'ucb2'" is not in the list of allowed feeds. There are no allowed feed URLs in the list. | 30 Nov 2010 | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet. Feb 2011: UCST invited the providers of reusable tools to comment on the requirement 1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". |
3.Fixing the known bugs before adding new features | Extension:RSS -- Error: "https://service-requirements:Teoer02i@rt.egi.eu/requirements/Search/Results.rdf?Order=DESC&OrderBy=Created&Query=Queue%20%3D%20'requirements'%20AND%20'CF.{Custom%20Tag}'%20%3D%20'ucb3'" is not in the list of allowed feeds. There are no allowed feed URLs in the list. | 30 Nov 2010 | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet. Feb 2011: UCST invited the providers of reusable tools to comment on the requirement 1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". |
4.Coherency of command line commands, parameters and APIs | Extension:RSS -- Error: "https://service-requirements:Teoer02i@rt.egi.eu/requirements/Search/Results.rdf?Order=DESC&OrderBy=Created&Query=Queue%20%3D%20'requirements'%20AND%20'CF.{Custom%20Tag}'%20%3D%20'ucb4'" is not in the list of allowed feeds. There are no allowed feed URLs in the list. | 30 Nov 2010 | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet. Feb 2011: UCST invited the providers of reusable tools to comment on the requirement 1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". |
5.Better feedback about jobs, automated resubmission of jobs that are stuck on sites | Extension:RSS -- Error: "https://service-requirements:Teoer02i@rt.egi.eu/requirements/Search/Results.rdf?Order=DESC&OrderBy=Created&Query=Queue%20%3D%20'requirements'%20AND%20'CF.{Custom%20Tag}'%20%3D%20'ucb5'" is not in the list of allowed feeds. There are no allowed feed URLs in the list. | 30 Nov 2010 | Jan 2011: UCST asked ticket submitters to provide technical details about the circumstances under which the scalability and stability problems were experienced: no updates received yet. Feb 2011: UCST invited the providers of reusable tools to comment on the requirement 1st of April 2011: UCST sent reminder to those who didnt replied. Still they have 20days to reply, after the ticket will be set to "Resolved". |
Requirement Status | ||||||
---|---|---|---|---|---|---|
UCB Requirements | New | Open | Accepted | Stalled | Resolved | Rejected |
Requirements are discussed at UCB
Board Tag: UCB
Status at TCB
Requirement Status | ||||||
---|---|---|---|---|---|---|
UCB Requirements | New | Open | Accepted | Stalled | Resolved | Rejected |
Requirements were discussed at UCB and transfered to TCB
Board Tag: UCB_TCB
User Support Status
Requirements in process by User Support
Board Tag: Not equal to UCB, UCB_TCB
Current Statistics
- Example.jpg
User Support tickets per Category
- Example.jpg
User Support tickets per Requestor
- Example.jpg
User Support tickets per Status
History Statistics
- Example.jpg
User Support tickets per Category
- Example.jpg
User Support tickets per Requestor
- Example.jpg
User Support tickets per Status
- Example.jpg
User Support tickets per Category
- Example.jpg
User Support tickets per Requestor
- Example.jpg
User Support tickets per Status
- Example.jpg
User Support tickets per Category
- Example.jpg
User Support tickets per Requestor
- Example.jpg
User Support tickets per Status
- Example.jpg
User Support tickets per Category
- Example.jpg
User Support tickets per Requestor
- Example.jpg
User Support tickets per Status