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; } } }

Can you enforce having to fill a form on jira when moving a column

Adi Shik

I want to have the option to force a person that is moving a task to Rejected(Column) to fill out a bug form, is it possible?

Accepted answers

Ste Wright

Hi @Adi Shik

Depends what you mean by Form - if you mean actual Forms, then as far as I know these are only possible to use during issue creation in JSM.

If however you mean a Screen (with a set of Fields) a user needs to populate, then you can do this within your Workflow.

---

Assuming this is a Company-managed Project, you will need to:

Create the Screen, and add the fields you require a user to populate to it - see this set of help pages
Add the Screen to the relevant transition(s) to the Status(es) in the "Rejected Column" - see this help page for how to do this
Use Workflow Validators on each transition to make fields mandatory during the transition(s) - eg. Make Field Required Validator. See more on how to set Validators on this help page

---

For Team-managed Projects, you can't do all the same steps as above - this is because you cannot have transition screens in the workflow. There is a feature request for this though you can vote for/watch, see: JSWCLOUD-22084

You can add Workflow Rules though, including the rule Restrict to when a field is a specific value - in effect, stop users from transitioning the Issue until the fields are populated/set.

You can see more on Team-managed workflow rules on this help page

---

Let us know if this fulfils your need!

If you'd like any more specific instructions for any stage above, let us know!

Ste

All comments

Ashley Hudson_r44fsl

Heya @Adi Shik

So if you want to enforce users to fill out a form, a solution could be to create an automation rule within the project that whenever a user transitions to rejected, then create a transition screen where users will input your "form fields" within the screen. To allow the form to be filled, you would need to link your form fields to a corresponding Jira field. That way the selection is stored in a value that automation can pick up!

I hope this helps!

Kind Regards,

Ashley Hudson

Ste Wright

Hi @Adi Shik

Depends what you mean by Form - if you mean actual Forms, then as far as I know these are only possible to use during issue creation in JSM.

If however you mean a Screen (with a set of Fields) a user needs to populate, then you can do this within your Workflow.

---

Assuming this is a Company-managed Project, you will need to:

Create the Screen, and add the fields you require a user to populate to it - see this set of help pages
Add the Screen to the relevant transition(s) to the Status(es) in the "Rejected Column" - see this help page for how to do this
Use Workflow Validators on each transition to make fields mandatory during the transition(s) - eg. Make Field Required Validator. See more on how to set Validators on this help page

---

You can add Workflow Rules though, including the rule Restrict to when a field is a specific value - in effect, stop users from transitioning the Issue until the fields are populated/set.

You can see more on Team-managed workflow rules on this help page

---

Let us know if this fulfils your need!

If you'd like any more specific instructions for any stage above, let us know!

Ste

Tessa Tuteleers

Hi @Adi Shik

Welcome to the community!

moving an issues from one column on your board to another is basically transitioning the issue from one status to another.

For such a "transition", you can put a screen with fields on it, and add validators (before you can complete the transition, validate that a condition is met).

How you have to do that depends on whether this is a company managed project, or a team managed project. (I added the documentation links).

So if you add the fields to the transition, you can add the necessary information. You can then create a new bug issue with that information by using an automation rule (when issue transitioned, create new issue)

Let me know if you can't work it out!

- Tessa

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

forms