John Funk Community Champion

Please contact the vendor for support with their product. 

Thanks for the screenshot. You cannot control who the assignee is using this method. If there is no default assignee, it will be unassigned. 

So no users show up? Or only some users, but not the one you want? 

What is the step by step process you are doing to create the issue? 

Hi Ziad - Welcome to the Atlassian Community! Yes, you can certainly do that. 

Ah, have you contacted the Snyk vendor for assistance since they are the ones routing through? 

Hi Nerusu, What do you mean by it is having performance issues? What is happening that leads you to believe that? What action(s) do you believe is triggering this behavior? 

Hi @Bala There are probably a couple of ways to accomplish this. One is to create a custom field for QA Tester or QA Analyst as a single user picker field. Then you can populate that field at any time. Then I would create a board using a filter where that custom field is not empty. Then on that board, you can drag the…

Hi Dominic, You can control who can create issues in your project with the Permission Scheme. Moving an issue into another project is actually a create function and needs that permission. So adjust the Permission Scheme used by your project to not allow others to create there. 

Hi Sunoop, Did you start typing the user's name? It should appear then. 

Hi Arun, If the page us blank, that would tell me that you have not archived any projects yet. 

Hi Nasiruddin - Welcome to the Atlassian Community! Use the Scheduled Trigger. Try that and post your rule here if you have problems. 

Sure, you can add multiple fields to the form including paragraph/multi-line text fields to capture the data. 

Just curious, but why can't you use this solution? I don't think you are fully understanding my suggestion. 

Hi Marcin - Welcome to the Atlassian Community! Go to Project Settings > Details. There you will see the Default Assignee. Change that value to Unassigned. 

Thanks for the information. Please reply inline here so that users can follow the conversation. Go to Settings > Issues > Custom fields and search for the Customer field. Then look to see if it is attached to any screens. Then click on the 3 dots to the right and click on Default Value and Contexts. Once there, see if the…

Hi Steven, How are you determining if there is a "conflict"? 

Hi Ayush, Forms in Jira do not allow users to create/add fields. Forms are intended to guide users to provide the exact information needed by the help desk people to solve their problem. 

Hi @Mguiss_ Anis _AllianzGI_ Do something like below:

Well, that's not good. Are you on Jira Cloud, Server or DC?

You are very welcome!

Hi Sunoop - did you start typing a name in there? Something should show up then. 

There we go! That last one. Click the box for Allow rule trigger. Save and Publish. That should do the trick for you that when the Sub-task changes, it updates the Parent. When that Parent changes, it should now update the Epic automatically. :-)

Hi Dan, You might try an automation rule like below. I have not tested it so you will need to do that. 

So the progress above says 60%. Does it not get past that? Have you tried on another browser or with Incognito window?

Yep - but can you do the screenshot of your Rule details for the second one? 

Okay, I think I understand better now. A user sends an email to particular email address. The Jira email handler kicks in and creates an issue in Jira. But the Description field shows the information from the email in a table instead of just plan text. Is that the case? Is it the signature that is showing up in this table?…

You can't just make it appear like that. My suggestion is above is not to escalate it but move it into a new status prior to escalate which would make the Escalate option appear at that point. 

:-) The work around would be what @bmccoy mentions below. Export the rules and then import under the new project. 

Okay, if I am following you - add a Branch at the very end for Most Recently Created Issue. Then under that add a new action for Link Issues. Choose the Link type that you want and then use Trigger Issue. This will link the Bug you created to the originally created issue that started the automation.