nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira workflow toolbox: marking linked issues field required

Scott McDonald_qykakt

I want to require the user to complete the Linked Issues/Issues field when transitioning in a workflow. What is the command/option I will want to choose in the workflow toolbox add-on? Thank you.

image2016-8-31 17:56:11.png

Update parameters of the 'Validation on linked issues' Validator for this transition.gdoc

UpdateparametersoftheValidationonlinkedissuesValidatorforthistransition.docx

Accepted answers

All comments

Fidel Castro

Hi Scott,

Do you want the user to create at least an issue link when transitioning an issue?

Are you interested in require a specific issue link type and/or issue type of the linked issue?

Scott McDonald_qykakt

Hello -

I have added the Linked Issue field to the transition screen and want to make that field required so they can add an linked issue..The use case is the expected behavior is the tester could not press the [Pass]button unless there was a linked test case.

Thank you.

Fidel Castro

You should add "Validation on linked issues" validator to the screen transition with a configuration like the following one:

Issue Link Types: check the issue link type you want for linking to Test case issues.
Issue types for linked issues: Test case
Statuses for linked issues: don't check any (I'm assuming you don't want to apply restrictions on linked issue's status).
Resolutions for linked issues: don't check any
Filtering by field values: leave it empty
Minimum required number of issue links: 1
Maximum allowed number of issue links: 9999
Allow unselected issue link types: CHECKED
Allow unselected issue types: CHECKED (I'm assuming that the issue link type used for Test cases can also be used for linking other issue types.
Allow unselected statuses: CHECKED
Allow unselected resolutions: CHECKED
Allow unsatisfied condition on field values: UNCHECKED

Scott McDonald_qykakt

That did the trick! For extra credit, I even added a message for them to add an issue.

Thank you!

Scott McDonald_qykakt

I am trying to link an issue type by entering the ticket number and it's not allowing me to move to the next screen. Within my Validator, I have the Issue types for linked issues set to Bugs and Test so in theory, as long as the issue type is either one of those, I should be able to link it, correct?

Scott McDonald_qykakt

Actually, I played around with additional settings and I was able to link the issue

Bart Gundersen

I am having an issue with the below validation - can you please help?

Validation on linked issue:
At least 1 and no more than 1000 issue links with the following characteristics:
- Issue link types: Impacts or blocks.
- Linked issue's issue type: Artifact.
- Linked issue's status: Unit and / or Integration Testing, QA/UAT Support, New, Ready For Prod or Active.
- Linked issue's resolution: any
- Linked issue belongs to projects with keys: DA
About the rest of issue links:
- Unselected issue link types are allowed.
- Unselected issue types are not allowed.
- Unselected statuses are allowed.
- Links to issues in any other projects are allowed.
Message to show when validation fails: "A Testing Defect MUST be linked to a Deployable Artifact (either Impacts or Blocks) when transitioning from RCA to In Development".

The above always fails unless "Unselected issue types are allowed". Please note that I only want to allow Impacts or Blocks issue types.

Thank you for your help,

Bart

Bart Gundersen

Note that the below validation, on CREATE, on a different workflow works as I would expect - ie: the link type MUST be "Is a Deliverable of" and the issue type MUST be a "Higher Level Initiative".

Validation on linked issue:

At least 1 and no more than 1000 issue links with the following characteristics:
- Issue link types: Is a Deliverable of.
- Linked issue's issue type: Higher Level intitiative.
- Linked issue's status: Active.
- Linked issue's resolution: any
- Linked issue belongs to projects with keys: HLI
About the rest of issue links:
- Unselected issue link types are not allowed.
- Unselected issue types are not allowed.
- Unselected statuses are not allowed.
- Links to issues in any other projects are not allowed.
Message to show when validation fails: "When a BTD is created it must be linked to an Active HLI via the link type "Is a Deliverable of"".

Fidel Castro

Hi Bart,

I have some questions:

Is the validator in the workflow of issue type Testing Defect?
Do you have a type Deployable Artifact? In the message you use that name, but you have selected Artifact.
Do you allow Impacts and blocks issue links to issue types different from Artifact?

srikanth_ccx

Hi Fidel,

I am working for Bart. Bart is not available at this time so for quick resolution I am responding

Please note my comments below:

Is the validator in the workflow of issue type Testing Defect?
-> Yes,validator is in the Testing Defect workflow.
Do you have a type Deployable Artifact? In the message you use that name, but you have selected Artifact.
-> yes we do have a Deployable Artifact project and Artifact is an issue type init.
Do you allow Impacts and blocks issue links to issue types different from Artifact?
we don't want to allow impact and blocks issue links other than Artifacts.

Thanks,

srikanth

Juby John

Can you provide me configuration for validation on linked issue for below given

usecase

Parent Bug can only be closed if all the child issues are closed.

Fidel Castro

Hi Juby,

Assuming that when you say child issue you mean sub-tasks, you can use "Validation on subtasks" with the following configuration:

Subtask's issue types: don't select any option.
Subtask's statuses: select "Closed", "Done", "Resolved", or any other status you use for considering that sub-task is closed.
Subtask's resolutions: don't select any option.
Filtering by field values: leave this parameter empty.
Minimum required number of subtasks: 0
Maximum allowed number of subtasks: 9999
Allow unselected issue types: CHECKED
Allow unselected statuses: NOT CHECKED
Allow unselected resolutions: CHECKED
Allow unsatisfied condition on field values: NOT CHECKED
Skip validation when: Don't check any option.
Message to show when validation fails: "There is at least a non-closed sub-task."

Juby John

Hi Fidel,

Thanks.

By child i meant links, The sub task part i got it.

Thanks for helping.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

workflow

addon-com.fca.jira.plugins.workflowtoolbox.workflow-toolbox