I've created a custom field (WireframeID), and I'd like for it to be optional on a Task issue type that's using the default screen, but required on a custom screen that I've created (Test Scenario). I think I should be able to do this with a field configuration scheme, but I'm just not seeing how to get there. Any suggestions?
Denise, I think you need to go another way here.
You want to make it required on a specific transition screen. That's different than making it required for a field, so you wouldn't do this in the field configuration. You'd want to do this inside the workflow. Find the transition in your workflow that triggers that specific screen and make a condition that the field is required. If you need more specific instructions, please let me know.
if you want to make field required through field configuration then follow the following steps
1. go to the project administration page
2. click on the field configuration which you have assigned to the specifific issue type under field configuration scheme
3. go to the field and click on required option which is located right side of the field
check here for mor einformation(Making a field required or optional)
another way you can make field required by using "field required" validator which is availble on JSU plugin, check this document
I've currently got the field set as required using the field configuration. What I'm running into, specifically, is that even though it's not available on the default screen, it's still pulling as required. The more I've thought about it, I'd like to have it display on the default screen, but there, I'd like it to be optional.
The WireframeID field is associated with the Task (Dev) issue type, as well as our Test Scenario Issue type. It appears on the Test Scenario screen as a required field. It does NOT appear on the Task (Dev) screen, but since it's required, it breaks the Task (Dev) screen. We'd like the WireframeID to be an OPTIONAL field on the Task (Dev) screen, but REQUIRED on the Test Scenario screen.
After additional debate with one of my collegues, we've decided (at least for the time being) to have it be required on both fields, so that both developer and tester have it as a frame of reference. I'm going to keep this as an option for if/when we decide to change it going forward. Thanks everyone.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot