Rally Software

Expand all | Collapse all

Traceability Between Change Request and Feature

  • 1.  Traceability Between Change Request and Feature

    Posted 02-24-2017 10:09 AM

    How do you create traceability between a change request from an ITIL Change Management system and a Feature in Agile Central? Currently we use Cherwell for our ITIL processes and require teams to create a Production change request. Right now we have a list of change requests and a list of Features, and need to make the connection between the two to get a full TECH and Business change impact. Any suggestions is appreciated!



  • 2.  Re: Traceability Between Change Request and Feature

    Posted 08-25-2017 05:07 PM

    Hi Amanda, Could you put the change request number from Cherwell into the Feature and put the formatted ID  (F1263) into the change request so that they are cross referenced?  Within Agile Central, how about creating a custom field called CRnum to hold the change request number?  Then you can do filtering and searching of that field?  

     

    Create and Customize Fields | CA Agile Central Help 



  • 3.  Re: Traceability Between Change Request and Feature

    Posted 11-30-2017 09:33 AM

    Thank you Edwin! Yes, that is what we are planning to do - develop a two way relationship through Feature ID and Change Request ID. Was curious to see if anyone had integrated Agile Central with a Change Management, specifically Cherwell. Would be interested in having a conversation about their solution.



  • 4.  Re: Traceability Between Change Request and Feature

    Posted 05-13-2019 09:21 PM

    Amanda,

     

    I know that this is an old topic, but I'd be curious to know if you advanced any further on this than just cross referencing by ID number?