Skip to main content

Require details for urgent work

Make sure every urgent work item in a space has a due date and a description before work starts on it.

Problem: People raise Highest work items with no due date and no description. Your team then chases the reporter to learn what's needed, and by when.

Solution: You add a UI modification that asks for the details while people fill in the form. Then you add a validator that blocks the transition when the due date is still missing, however the work item was created.

What you'll need​

  • Script Master for Jira, with an active license. See Get started.
  • The Administer Jira global permission.
  • A space, for example DEMO, whose workflow you can edit, with a transition that starts work, for example Start progress.
  • No Companion App: UI modifications run in the browser, and Jira evaluates validators.

Set it up​

1. Ask for the details on the form​

  1. In Script Master, select the UI Modifications tab.

  2. Select the arrow next to Create UI modification (More ways to create) and select From a template. The Start from a template dialog opens.

  3. Select Require details for urgent work. The editor opens with the template switched off. Its rule says: when Priority is Highest, show and require Due date, and require Description.

  4. In Where it runs, select DEMO in Spaces. Keep Create and Transition screens in Forms.

  5. Below the rules, select Try it, set Priority to Highest, and check that Due date and Description are marked as required.

    The UI modification editor with Where it runs set to DEMO and the Require details for urgent work rule under IN PLAIN WORDS

  6. Turn on Enable, then select Save.

2. Block the transition without a due date​

The form change helps people who use the Create dialog. Board inline create, the REST API, automation and bulk edit skip UI modifications, so a validator enforces the rule on the workflow.

  1. In Jira's workflow editor, open the workflow of space DEMO and select Start progress.

  2. In the rules panel, select Add validate details rule, then Scripted Validator and Select. The Script Master editor opens with Build with rules selected.

  3. Select Add a check, then choose Due date and is set.

  4. Under Only check when, select Add a condition, for example work type or space. Choose Priority, is one of and Highest.

  5. In Message when it blocks, enter Set a due date on [Work item key] before you start it.

  6. In Test on a work item, pick a Highest work item with no due date and select Run test. The result reads Blocked, with your message.

    The rule builder with Due date is set, Only check when Priority is one of Highest, and a Blocked test result

  7. Select Add, then Update workflow.

What your team will experience​

  1. A reporter creates a work item in DEMO and sets Priority to Highest. Due date appears and, with Description, becomes required.
  2. Someone creates an urgent work item another way, for example through automation, with no due date.
  3. When a team member tries Start progress on it, Jira blocks the transition with the message, for example Set a due date on DEMO-12 before you start it.
  4. Work items with any other priority pass the validator as before.

Check that it works​

  1. In DEMO, open the Create dialog and set Priority to Highest. Confirm that you can't create the work item without a due date and a description.
  2. Create a Highest work item with no due date from a board's inline create, then select Start progress. Confirm that Jira blocks it with your message.