Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Howzit,
We are working on a maintenance ticket in Jira Service Management Data Center that must contain a customized list of tasks based on the type of maintenance work (maintenance block) and the category of the device.
When the maintenance due date arrives, a ticket is supposed to be generated that contains:
- the maintenance device name
- the maintenance due date and
- the list of tasks to be performed.
All possible tasks have been added as objects to the database. Currently, they have been given a unique maintenance block as an attribute and another attribute contains the possible device categories they might apply to. As mentioned, the device category determines which tasks from the maintenance block actually have to be performed.
e.g., Maintenance block 1
=> Out of all the Maintenance Block 1 tasks, only Tasks 1, 2, 5, 6 and 8 must appear in a ticket for a Category 1 device.
e.g., Ticket details:
How should the database be configured so that we can set up a rule that can assign the right set of tasks from the maintenance block per category?
Have a good weekend!
Paul
Hi everyone,
we found that our existing database structure allows us to run the necessary AQL-query:
"Relevant device category" IN ("[DEVICE CATEGORY]") AND "Checklist name" IN ("[CHECKLIST NAME")
The next step would be to use the query to populate a Custom Assets Field in Jira?
Best regards
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.