Severity missing from RTC 2.0 Scrum Tasks?

Mark Ingebretson wrote:

It appears that the severity field is no longer displayed in task work
items in Scrum 2.0. I see that Scrum 2.0 tasks don't use the default
Editor Presentation, and there's now a com.ibm.team.workitem.editor.task
version. The Details section doesn't include the Severity field. Why
is that? It is part of the default Editor Presentation.

Another similar issue. The Workflow Resolution field exists in the RTC
2.0 default Editor Presentation Editor Header section, but it isn't
included in the Task version Header section. Shouldn't that be included
in the header for tasks?

Mark Ingebretson wrote:

Mark Ingebretson wrote:
It appears that the severity field is no longer displayed in task work
items in Scrum 2.0. I see that Scrum 2.0 tasks don't use the default
Editor Presentation, and there's now a
com.ibm.team.workitem.editor.task version. The Details section
doesn't include the Severity field. Why is that? It is part of the
default Editor Presentation.

Another similar issue. The Workflow Resolution field exists in the RTC
2.0 default Editor Presentation Editor Header section, but it isn't
included in the Task version Header section. Shouldn't that be included
in the header for tasks?

OK, I think we can just add the severity field back into the Details
section of the Task Editor Presentation.

But it appears to me like there's been a larger change to Scrum 2.0 in
which the Workflow Resolution field is no longer used, except for
Defects. Is that correct? I didn't see this documented anywhere, or
maybe I missed it.

How can you "delete" a task by setting it to Closed/Invalid with no
resolution field?

Thanks!

Any Scrum 2.0 people out there?

One of our goals for RTC 2.0 was to improve SCRUM support. This lead to changes of the process templates, which were tracked in story 79687 (https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/79687).

As for your specific questions:
- The severity was removed from the task type, as it was primarily intended to denote the severity of defects. If you use the field for other purposes, you can add it back at any time
- The resolution of tasks were hidden as they are usually not of interest. There is a "Invalidate" action, which leads to an "Invalid" state, in case you want to "delete" a task.

The SCUM process template is a good start when using the SCRUM process, but you can always modify the process specification to match your very specific needs.

--
MikeS
Jazz Agile Planning team

Mark Ingebretson wrote:

Mark Ingebretson wrote:
Mark Ingebretson wrote:
It appears that the severity field is no longer displayed in task
work items in Scrum 2.0. I see that Scrum 2.0 tasks don't use the
default Editor Presentation, and there's now a
com.ibm.team.workitem.editor.task version. The Details section
doesn't include the Severity field. Why is that? It is part of the
default Editor Presentation.

Another similar issue. The Workflow Resolution field exists in the
RTC 2.0 default Editor Presentation Editor Header section, but it
isn't included in the Task version Header section. Shouldn't that be
included in the header for tasks?

OK, I think we can just add the severity field back into the Details
section of the Task Editor Presentation.

But it appears to me like there's been a larger change to Scrum 2.0 in
which the Workflow Resolution field is no longer used, except for
Defects. Is that correct? I didn't see this documented anywhere, or
maybe I missed it.

How can you "delete" a task by setting it to Closed/Invalid with no
resolution field?

Thanks!