Not Able to close Multple Change Tasks through the list view
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 02:23 AM
Hi SNC team,
It would appear that regardless of roles (admin) We are not able to change the state of multiple changes from Open to Close. We get the greyed out security prevention message.
In looking at an answer from back in 2016 it talks about Highlighting in the list view and changing - this is what we can't do, It also shows a screen shot where the boxes are ticked and then you go to actions on selected rows and it shows a Close task option. It would appear that this no longer exists.
Does anyone have any ideas on how this can be done in bulk without the need to do any importing - which is bit of a pain.
We are talking 100s at a time, so to do it individually is terribly time consuming,
Do you have to be in the ITSM scope - rather than global or customer service?
Any ideas would be great

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 02:32 AM
When you try to close a change task, the closure information fields are mandatory, hence ACL restricts you to close through list view, if you want to close multiple task, the only way is to run a background script or have a schedule job to run daily and close the task and change request .
Harish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2023 02:40 AM
Thanks @Harish KM , thinking about it now there is an OOTB Mandatory closure fields in a couple of task - I am assuming if they aren't mandatory then we can close the tasks
if so then we will have to make the necessary changes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2023 01:09 AM
Just to advise anyone looking at this - we have found out what was preventing the closure of multiple closure of Change tasks and then subsequently the Change. This is due to the fact that we are importing the Closure state and in doing that the task was still showing as Active - in making it InActive then the Change will also close.
Hope that is useful to other members of the community.