Best practice use of work item State and Resolution fields
We use a multi-step development workflow process that moves work items through various stages of Development, Quality Assurance, and Production deployment with accommodation for build requests, software deployments, and defect fixes in between. I am envisioning all these stages as "States" in RTC. However, a coworker envisions breaking these up between State and Resolutions.
What is RTC's intent of how State and Resolution should be used? Why does it matter? I assume if we follow RTC's intent and best practices we'll be better served in the long run. Are these best practices documented anywhere?
One answer
Hello Michael,
this is more a generic agile question to, rather that a RTC specific one.
I guess it all depends on your business constraints:
- resolutions might not be visible for all states
- resolutions items might differ depending on state
You may want to refer to https://jazz.net/library/article/1002,
Hope it helps.
Eric.