Forum Discussion

MartinH_1's avatar
MartinH_1
Occasional Contributor
15 years ago

Change Requests - Not Defects

Hi, We have been using SoftwarePlanner for over a year and are interested in what is considered the best practise for managing Change Requests within SoftwarePlanner.   Currently, they ente...
Ssardo's avatar
Ssardo
Contributor
14 years ago
Hi.

I've quite the same need:


  1. a user (or even a guy of working team) inserts a new item in "defect", supposing it's a real defect

  2. an analyst lokks at the new item and decides to "route" it to a "Request for change" (or "implementation") issue

  3. In the real world the "Implementation" workflow is not equal to "Defect workflow", and could have different user-fields and even statuses

  4. currently, in cases like this, it seems I have to "move" this new "defect" item into "Requirement" issues, but I could loose fields, values, status, and even links. Anyway an "Implementation request" is not logically equal to a "internal requirement" (ie: it has to be approved to become an internal requirement),... and the problem reappears again....


I think a new "label"/Category should be inserted, soon or later, in ALMComplete: something like "Implementation request" or "RFC" (better a shorter name...), with a strong relationship with "defects" issues (easy copy/move between them, same user-fields to avoid looses in migrating, different workflows,...).



Best regards!