Process with optional child tickets
Allow selection of which child tickets will be created when creating a new parent process ticket. This would allow child tickets to be optional, either based on conditions defined in rules, or at the ticket creators discretion. For example, in a new user creation process, some users may not require an account on a specific system. It should be possible to start the process but exclude the creation of the child ticket for that task.
Michael McNally
shared this idea
-
Nancy Cunningham
commented
It would be helpful to be able to add new child tickets into a process template that are only used in 'future' processes. For example, we occasionally need to make changes to our on-boarding processes, which requires adding or removing child tickets. The problem with adding new child tickets is that if an old/completed process is edited (for example - a comment is added), the new child ticket is automatically added into that old process.
In addition, it would also be helpful if we were able to 'disable' a child ticket (instead of having to delete it from a process template) in case it would need to be re-enabled in the future. I have had this happen, and we had to recreate several process templates and 'retire' the old ones, which would have been unnecessary if I could have simply re-enabled that child ticket.
-
Nancy Cunningham
commented
This option would allow some flexibility so we would not have to create as many processes. For example, technology services that need to be set up for new employees will vary based on the type of position.