I know I've done this before, but I can't figure it out now. I have some fields that I put on a transition screen, and when that transition is made, I want the fields to be required. I also want those fields on my edit (and view) screens, but I don't want them required on the edit screen (you may be editing before you know how to fill in those fields).
Can someone please remind me how I managed to do this in the past? Thanks!
Please don't have a go at people for making suggestions for "use an add on" when there is nothing built into the product.
If you read the answer and comment properly, there's no sales pitches here, it is purely "it can't do it natively, have a look at some add-on options".
Also, note that the JIRA Suite utilities are free. So it's not like that answer was sales either.
And, yes, there's now something on the roadmap. So having a go at people for 3 year old answers when there wasn't anything on the roadmap is just silly.
Agreed, @Nic Brough [Adaptavist]. @David Skreiner - there is a lot of functionality that developers of plugins provide that Atlassian either can't or won't. No one is peddling, they are answering questions and providing solutions that otherwise wouldn't exist. You must be new to the forum, because I've been here for years and many questions are answered by the use of third developer plugins.
@Natalie Hobson You must have a really huge budget if you don't mind that most of the answers on "answers" are "go buy a plugin, we're not fixing this". I don't, and it's frustrating to have to keep telling colleagues that I ca't implement something because we're not buying more plugins.
@David Skreiner I never said that I didn't mind the fact that there is a lot of functionality that would preferably come straight from Atlassian; that's just how it is. And you telling other people not to recommend plugins when they are sometimes the only solution is a ludicrous suggestion.
This forum is for assisting other Atlassian product users - it doesn't sound like you are here to help, but to complain. Please take your complaints directly to Atlassian, as there's nothing that complaining here can do for you productively.
The fact that the "answers" page contains mostly suggestions to buy a plugin causes intense frustration to JIRA admins and contributes to Atlassian's reputation of money-grubbing plugin-salesmen who don't fix issues in their product if there's paid plugins to fill the hole. I didn't invent this, I got warned about this in both JIra Admin courses that I took, years ago.
So this policy harms Atlassian's reputation and frustrates customers. I think it would be an excellent idea to split the Help pages into an Atlassian Products help section, and another section that sells paid plugins.
(And of course its fairly obvious that people who write and sell plugins don't like customers to point this out. I agree it's the wrong place though, so I'll try to shut up.)
Yet again, you're completely missing the point.
The vast majority of the answers are not selling, they're offering ways to help people achieve things (or sometimes, telling them that they simply can't). When add-ons are mentioned, it's rarely sales text, it's because they're a good way to achieve a goal.
Splitting it in two is a silly idea. No one would go to the sales site naturally, because they don't know that they might need an add-on until they're told they might. And then the answer "go read another unrelated site" is clunky and you'll simply confuse users more when you say it. If there's a good answer that's along the lines of "use an add-on", why should i not post that ans an answer? It's correct, it's valid and it's helpful.
Hi @Nic Brough [Adaptavist] , if the add-on is broken , why it's working fine with other fields ? and I removed any custom field that has original Estimate as part of the field name but still having same problem. is it something related to how Jira is handling estimated effort field ?
I am trying to make a custom field required upon transition, however I do not see a "field(s) mandatory" option in validators. The only options I have are:
Am I looking in the wrong place?
Workflow Essentials for JIRA also has a Validator for that. It supports basically all Custom Fields and some system fields as well (Description, Affects Version, Fix Versions, Labels, Due Date, Comment). Additionally it will mark required fields with a red asterisk just like globally required fields.
You can refer to this page https://confluence.atlassian.com/jirakb/how-to-make-jira-applications-fields-required-in-a-workflow-transition-691011903.html to give the workaround or resolution a try.
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