are you on Server or Cloud?
The only sane reason for a delay would be that you're doing something asynchronously and want to wait for another process. However, a delay is the wrong answer in this case, you need to code your processes to talk to each other properly.
But, if you insist on doing it the wrong way, either create a condition that says "only if issue X was updated more than 5 seconds ago" or put "sleep 5s" into a post-function on the first transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for necroposting but one of the reasons to wait between transactions is to be sure that attachments were added to the ticket.
I'm facing problem that I need to copy attachments from Parent issue to Child one, but neither Copy attachments, nore additional transaction after create Issue doesn't help. Jira still doesn't see attachments and do not copy them.
My workflow looks that way: Create issue from email with attachments -> Transition it to next Status -> Self-return transition with creation of related issue and copiing attachments to new one. But withiout delay it doesn't work
If any one can suggest decision of this problem - it would be highly appriciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A delay is irrelevant here. You need to code for a validator to check attachments were added.
You've got a problem with whatever you are doing to copy the attachments, not a delay.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Forgot to mention that all transitions are triggered automatically, without user actions. That's why I expected to use "Delay" so Jira has time to attach attachments
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you explain what you have set up here? It makes no sense to have to "wait for attachments" - how are you attaching them? What are you doing that runs before the attachments are attached?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a project, where I create intermediate tickets from email with attachments. After ticket was created Jira creates child ticket in another project automatically and copies a list of fields. This is done with JMWE addon. The problem is that attachments are not copied. But when I perform this transition manually - all works well. It seems, that attachments appear in parent Jira ticket after the transition was performed, that's why I think about necessity of delay.
User, who performs automatical transition has all rights to create attachments
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, that's most of the process perfectly clear, but how are you triggering "after issue created, create issue in another project"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When issue created I trigger transition called "Next" where JMWE post-function: Crete/Clone Issues placed. It is first in the list.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so your "next" transition can only happen after the issue has been created, and that includes attaching things to it.
So that suggests that something is going wrong in the copy for this type of issue.
It worries me that you say the attachments only appear after you perform the next transition. That suggests something else is adding them to the emailed issues.
So I'm a bit stuck on this one.
There is a test you could do though; most JMWE post-functions have an option for "delay" on them - I think the last time I used it, we could go up to 10 seconds.
You could use that to confirm the "delay" theory. It'll annoy your users, as they'll have to wait too, but if it solves the problem, we can work around that!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Nic. The delay function was excluded from JMWE plugin for Jira Data Center edition as I mentioned above.
But you were right, there was a permissions issue for user who performed that action. Now it seems to work fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.