Anthony Albon Posted August 2, 2021 Posted August 2, 2021 Hi, I have set up change management under a separate service and it works fine for me and my team. However, members of our infrastructure team cant see the service when they try to create a change, they get this: Can anyone assist in resolving this, thanks
Adrian Simpkins Posted August 2, 2021 Posted August 2, 2021 Hi Anthony, When I see this it normally just indicates they are either not subscribed to the Change Service / are missing change roles / not a member of the Change team (if one setup) or a combination of all 3 depending on how your Change Service is configured, so I would double check this for the other team myself Many thanks
Anthony Albon Posted August 2, 2021 Author Posted August 2, 2021 Thanks, they do have the roles and I dont think we have a change team setup. Under supporting teams it says this service is supported by all teams. Am I missing something? Regards, Anthony
James Ainsworth Posted August 2, 2021 Posted August 2, 2021 Hi Anthony, Thanks for your post. I'd start with the Customer and the difference between Supported By and Subscribers. On a Service the Supported By option this should contain the teams that will be fulfilling the changes. Having this set to be supported by all teams is fine. In order for members of these teams to raise changes they will need the appropriate Server Manger roles for change management. The Subscriptions on a service are typically the users or customers that you are fulfilling the changes for. In the screen shot that you provided I see that there is a customer (Subscriber) that was selected in the first step of progressive capture. There will also be someone that is raising this change (Support By team member). There is some logic within Progressive Capture that determines what is displayed on each form based on previous selections. In your example because a customer has been selected using the Customer Progressive Capture form, the Service Details form is looking a the services that the customer is subscribed to. Even if the person raising the request is a member of the Support by team has the rights and roles to raise changes, they are not seeing the service, because this customer they are raising it against is not subscribed to the service. If the Customer Progressive Capture form is removed, the Supported By team member should then see all the services. Customers are not a requirement for changes, but if you do want to capture customers for changes, then you need to make sure that they are subscribers to this service. There is a setting that can override this behaviour and show both the services that the user subscribes to and the services that Supported By team member supports, but keep in mind that this is a global setting and it may impact how other teams work when raising requests. I hope that helps. Let me know if you have any questions. Regards, James
Anthony Albon Posted August 3, 2021 Author Posted August 3, 2021 HI James, the person raising the change is part of our IT infrastructure team. He has all the change management roles assigned to him and the service is supported by all teams. However he still sees no services available to choose from?
Anthony Albon Posted August 3, 2021 Author Posted August 3, 2021 I made some changes and it gets to the next stage now for the person creating the change
James Ainsworth Posted August 3, 2021 Posted August 3, 2021 Hi Anthony, I'd need to see your Progressive Capture workflow to see what's going on there. This may be something configured incorrectly with branching or the switch nodes.
Anthony Albon Posted August 4, 2021 Author Posted August 4, 2021 OK thanks James, do I need to log a support call?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now