On a workflow a made attachment field required with "add validators to transition".
But after i publish the workflow and i want to move an issue from a status to another I receive an error message like this:
even if i attach a document.
I attach a document from:
but i have the same error and i really don't understand why?
Do you have any idea?
Thanks a lot,
It sounds like you have added this "make attachment mandatory" validator to all the transitions. That's fine in itself if you genuinely want to stop people using the workflow if they've removed all the attachments.
But it also sounds like you have used a validator that says "attachment added on this transition", rather than one that says "there are attachments on the issue"
With what add-on have you enabled this validator?
There's no way to make attachments mandatory in plain JIRA, so I reached for an add-on. As you're on Cloud, there are a couple that are available (without you needing to install them), and I suspect you've used the one from the JIRA Suite Utilities - I seem to remember that does "added on this transition", rather than "has to be present", which would explain why this is failing for you.
I also seem to be having the same problem in that I'm trying to make an attachment mandatory on a transition using the Fields Required validator in JIRA Suite Utilities (on the post function, I create a new issue through JJupin SIL and want to copy this attachment across to the new issue). The validator message comes up even if I have an attachment on the transition.
It seems like the Fields Required validator is checking the attachments on the issue rather than the attachments on the transition (which aren't added to the issue yet). Unfortunately, I'm not versed in writing my own plugins (or tweaking existing ones) so I'm a bit stuck.
(I'm still pretty new at this myself, but since no one else has commented since the last post...) Are you able (or have you tried) to add a custom field to hold the 'special' attachment and add that field to a custom screen for that transition? (If that's doable, then maybe you could make that *custom* field mandatory, and it won't have to be 'on the issue' yet?)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs