Tracking Development Issues

Discussion of any ITIL or related issues that don't fit well into any of the above.
Post Reply
User avatar
jjarka
Newbie
Newbie
Posts: 1
Joined: Mon Oct 31, 2016 8:00 pm

Tracking Development Issues

Post by jjarka » Wed Dec 07, 2016 11:41 am

I am looking for some help and direction here. We are currently having a discussion on how to track development and test environment issues within our ITSM tool. I have many team members wanting me to create a new test or dev CI for a Service, ex. Oracle Test or Oracle Dev. So they can track issues with these environments.

My viewpoint is that while these do impact individual productivity, these do not impact users ability to complete their jobs in support of selling products and services. Therefore these dev or test items should be tracked as requests as opposed to an incident, or break fix event.

I am looking for some feedback on how others handle these types of issues.



User avatar
Nuno
Itiler
Itiler
Posts: 8
Joined: Tue Jan 08, 2008 7:00 pm
Location: Lisbon

Tracking Development Issues

Post by Nuno » Fri Dec 16, 2016 6:04 am

Hi,

We deploy everything on test and production environment using the "Release" methods but we track every issue on dev and test environment using a specific tool to have all "problems" solved and controlled when we're going to deploy on production system.

Regards
Nuno Mendes Fernandes
Release Management (IPRC, SS, SD, ST, SO)

Post Reply