I want to detect the conflict of the existing tickets having Same date and time ie; (date and time field) while creating a new ticket that can able thrown an error when same date and time is selected.
This enhancement project will be to determine the best method for using some scheduling conflict detection logic in the project.
Problem: Today, when users create a new ticket in the issuetype of project, there is nothing that will determine whether or not the new tickets will conflict with an existing tickets that may have already been scheduled status.
Conflict Detection Logic:
POD (Multiple Select) ------> Custom field
POD Conflict Detection: If the ticket being created has the same POD# as a change already on the calendar the user should get a Yellow Pop-UP that states, “A change on this POD already exists on the calendar for this date & time. Please ensure your change does not conflict with existing change before submitting your ticket.”
DataCenter(Multiple Select) -------> Custom Field
DataCenter Conflict Detection: If the ticket being created has the same DataCenter(s) as a change already on the calendar the user should get a Yellow Pop-UP that states, “A change on this Datacenter(s) already exists on the calendar for this date & time. Please ensure your change does not conflict with existing change before submitting your ticket.”
Service Provider-----> Custom field
Service Provider Conflict Detection: If the ticket being created has the same Service Provider(s) as a change already on the calendar the user should get a Yellow Pop-UP that states, “A change for this Service Provider(s) already exists on the calendar for this date & time. Please ensure your change does not conflict with existing change before submitting your ticket.”
Multiple Conflict Detection: If two or more of these conditions are met the user should get a Red Pop-Up Warning that states, “Two or more conflicts detected (POD, DC, Service Provider) with an existing change. Please ensure your change does not conflict with existing change before submitting your ICC ticket.”
A user should not be denied the ability to create a change based on this logic, but simply receive a warning that their change may be in conflict with a previously scheduled change.
