Great content, thanks for the tips, especially the workflow method. Seems like most people on the community forums were just ignoring it and advising field configuration method instead, which not only seems to be more complicated but limited as well.
Using field configurations to require fields is fine when a field is required from the point of issue creation. However, if you want to require a field that isn't meant to be set until an issue gets to a specific status within the workflow, then you have to use the workflow configuration method. It would be nice if Atlassian would provide more configuration granularity around the field configurations.
I think there 2 other important considerations: How do both methods interact when editing issues instead of creating. What happens if I edit an issue that has no value in field A, but the field is now required?
I have watched a few Jira tutorials. I am specifically trying to figure out how to create "sections" (headers) so that I can create a relay system for tasks. A lot of our tasks are done as an assembly line for some of our team. I am interested in Jira because it is more streamlined than Clickup, Linear is too simple, Notion is okay but very complicated to do the build out and may not be what we need. How do I create these sections?!
Hey, Alex I created a new screen and a new field in this screen called "Title" The field “Title” should be shown as the title of the ticket after the creation how can I do that?
I want to change the feilds to mandatory only when the user selects a certain answer on the drop down and it should not be mandatory when they choose a different answer on the same dropdown ,how do i do that
Afaik you can't in Jira Cloud. 1. Maybe Scriptrunner Behaviors can do it but not sure. 2. You can use Jira forms in service Desk to make display or hide a mandatory field depending on another field selection (f.e. dropdown). This means the field would be mandatory if shown and if hidden, then it can't be filled (so maybe not 100% what you want) and this means users would then have to create tickets from the form link or service desk portal only. 3. There is one other workaround, and that is to create 2 new transitions, X and Y, AFTER the create transition and then you use conditions on each of them. On one it checks if field A is filled and only then allows transition X, and if field A is not filled, then it only allows transition Y.
To get more resources and get in contact with me check out this link linktr.ee/apetech
Great content, thanks for the tips, especially the workflow method. Seems like most people on the community forums were just ignoring it and advising field configuration method instead, which not only seems to be more complicated but limited as well.
Yeah, it's good to have options. Sometimes you process calls for fields to be required later in the process. . . not upon creation.
।।अःअं।।लललर
Using field configurations to require fields is fine when a field is required from the point of issue creation. However, if you want to require a field that isn't meant to be set until an issue gets to a specific status within the workflow, then you have to use the workflow configuration method.
It would be nice if Atlassian would provide more configuration granularity around the field configurations.
I totally forgot to mention that! Excellent point.
Thanks, very helpful!
Glad it was helpful!
I think there 2 other important considerations: How do both methods interact when editing issues instead of creating. What happens if I edit an issue that has no value in field A, but the field is now required?
how we can make date field mandatory while closing the defect on version 7.8.0
I have watched a few Jira tutorials. I am specifically trying to figure out how to create "sections" (headers) so that I can create a relay system for tasks. A lot of our tasks are done as an assembly line for some of our team. I am interested in Jira because it is more streamlined than Clickup, Linear is too simple, Notion is okay but very complicated to do the build out and may not be what we need. How do I create these sections?!
I didn't see the Field Required validator in Jira Server.
How to get ?
Hmm. Not sure. All my videos are for Jira Cloud. I don’t have access to Jira Server =(
Hey, Alex
I created a new screen and a new field in this screen called "Title"
The field “Title” should be shown as the title of the ticket after the creation
how can I do that?
You can't. That's reserved for the Summary. .. . which is the title of an issue.
Can we make system field as a required field? I want to make Priority field as a required field.
Yes, you can make a field like Priority required.
I want to change the feilds to mandatory only when the user selects a certain answer on the drop down and it should not be mandatory when they choose a different answer on the same dropdown ,how do i do that
Afaik you can't in Jira Cloud.
1. Maybe Scriptrunner Behaviors can do it but not sure.
2. You can use Jira forms in service Desk to make display or hide a mandatory field depending on another field selection (f.e. dropdown). This means the field would be mandatory if shown and if hidden, then it can't be filled (so maybe not 100% what you want) and this means users would then have to create tickets from the form link or service desk portal only.
3. There is one other workaround, and that is to create 2 new transitions, X and Y, AFTER the create transition and then you use conditions on each of them. On one it checks if field A is filled and only then allows transition X, and if field A is not filled, then it only allows transition Y.
How can I create a screen for the reolved status and add a mandatory field
can jira make a field percentage ?
hello alex
Hello =)