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...
Forum Discussion
Thanks for the response!
It partially answers the question really because what we would really like to see in SoftwarePlanner is the Defects section be renamed to something like "Issues" since in most software development a large proportion of items raised as defects actually aren't.
The above suggestions are great but they don't really help with managing
whether to make the change to the requirement or not in the first
instance. We'd like to see a Change control section implemented or failing that, be able to classify "Issues" as either a "Defect" or a "CR". (It would be a bit onscure to manage a CR as a checkbox inside a defect that appears on all reports as a defect. If there were an Issue type of "CR" then you could resolve and close the initial Issue report (currently a defect) by noting the number of the CR that was raised and then manage the CR in the change control system.
cheers,
Martin
It partially answers the question really because what we would really like to see in SoftwarePlanner is the Defects section be renamed to something like "Issues" since in most software development a large proportion of items raised as defects actually aren't.
The above suggestions are great but they don't really help with managing
whether to make the change to the requirement or not in the first
instance. We'd like to see a Change control section implemented or failing that, be able to classify "Issues" as either a "Defect" or a "CR". (It would be a bit onscure to manage a CR as a checkbox inside a defect that appears on all reports as a defect. If there were an Issue type of "CR" then you could resolve and close the initial Issue report (currently a defect) by noting the number of the CR that was raised and then manage the CR in the change control system.
cheers,
Martin
