Mandatory field that shouldn't appear

[Mikhail Puzhay-Chereda]

What i have:

1. Field, that i called Vendor.

2. Workflow, which have an option "send task to a vendor" with a mandatory field, which have to be filled with a vendor name.

3. Types of request, which, i dont know why, also get this mandatory field. And i cant delete it, because of "Cannot delete a field that is required by Jira or Jira Service Desk".

What i need:

1. When i create a task, i dont need the field "Vendor" to show up and dont need to be filled.

2. When i realize, that task should be send to another vendor through the Workflow, i want this field to show up and be mandatory.

What i have at this moment:

This field is shown up in both screens (when i create the task and when i send to vendor and it is mandatory. i can hide this field in the stage of creating ticket, but i have to fill it with any default value. But i dont want it to be like this.

Here are a lot of screenshots (i am sorry, my Jira is Russian, and ill try to give explanations):

1. Here are the field :Vendor (Вендор он Russian) which is bound to screen related to Workflow "send task to a vendor'

2. Here you can see, that field is mandatory and only bound to screen in Workflow:

3. Here are this particular screen of Workflow:

4. Here are this what is work fine and should work like that. When i push "send to the vendor", this screen appears and demand me to fill Vendor field:

5. But it also appears, when i try to make task (request) and it is mandatory and this is shouldnt work like that:

6. And i cant delete it, when i configure task (request):

Sorry for such a huge message, but i decided, that this many screenshots should help to realize what i want.

[Jack Brickey · Accepted solution]

You don’t want the field to be mandatory that is what is causing the issue. You want the field to be “required” for the specific transition in the workflow. 

1. Make the field optional
2. define a new screen that has the vendor field on it and any other desired fields for the transition
3. Edit workflow and edit the transition to vendor
4. Assign the new screen you created
5. add a Validation to the transition requiring the vendor field
6. publish the edited workflow

[Mikhail Puzhay-Chereda]

Ok, so, you mean, that i dont need to make field required and i should ad a "Validation"? Could you explain more about validation and where and how to make it?

Edited:

Ok, i guess i found. But this doesn't help me to do what i want

[Jack Brickey]

Correct you rarely, in my experience, want a field "required" beyond the Jira default system fields, like summary, etc. What you want to require the field to be completed during a specific transition. I don't understand why this does not meet your requirements based upon what you have conveyed but i'm not 100% aware of your requirements. The question is - How do you send the issue to the vendor? What I would recommend is that you create a status for this along w/ a transition. By doing so you can then achieve your goal, i think.

For example, lets say today your work flow is the basic TO DO -> IN PROGRESS -> DONE. You could change to add an optional in progress status for the vendor, e.g. AT VENDOR and you could have a transition (e.g. Assign to Vendor) from say both TO DO and IN PROGRESS to this new status. If you do this and you add in the screen and Validation to the "Assign to Vendor" transition you can enforce the requirement of the Vendor field.