John Funk Community Champion

So if I understand you, when the request ticket reaches a certain step in the workflow (i.e. status) then the issue should be cloned into the engineering project. Correct? If so, you can create an automation rule based on an Issue Transitioned trigger. Choose the status that it is transitioning into. Then add any…

You are welcome. 

Can you elaborate? 

You are welcome!

Hi Consultant - Welcome to the Atlassian Community! In Jira you cannot have multiple levels of sub-tasks. All sub-tasks are at level -1.

Hi Michael - Welcome to the Atlassian Community! You will need to have Org Admin or User Access Admin permissions. Go to Settings (gear icon in upper right) > User Management Then click on Groups on the left side. 

Hi Sabina - Welcome to the Atlassian Community! Just add a column to your CSV for Parent. Then put the issue key of the existing Parent into that column for the sub-task. For example, ABC-123 Summary Parent Sub-task 1 ABC-123 Sub-task 2 ABC-123 Sub-task 3 ABC-123

Haha - glad that worked for you and you are welcome!

Then you can add the information panel like suggested by Brant and Rebekka. 

Hi Vitaliy - Welcome to the Atlassian Community! So, Jira Work Management and Jira Software have been merged into just Jira. Now those projects types are called Business and software. They are making the List view a part of the Software projects already. And Calendar is coming. So I would encourage you to use Jira Software…

So the query works great except for the status part? Try doing just status in (Open) and see if that works. If so, then add one at a time until it quits working.

Hi Sergei - Welcome to the Atlassian Community! Take a look at this: https://jira.atlassian.com/browse/JSDCLOUD-14326

Hi Alvaro, Add the Attachment field to your transition screen and see if that solves it. 

As a kid, I remember fireworks - especially bottle rockets - we would have wars with those. :-) And always watermelon. Usually my father grilled out hamburgers. But regardless, there was always watermelon!

You will need to query for the Sub-tasks if so, then do a Bulk change to move them to Stories. Then you can update the Parent field to your new Epic. 

Hi Moshe - Welcome to the Atlassian Community! Stories cannot have Tasks under them. Do you mean Sub-tasks? 

If they are not an Org Admin or have User Access Admin permissions and you are an Org Admin, then I would open a support ticket with Atlassian to find out what is up. Please post back here with the resolution. https://support.atlassian.com/contact/#/

You are welcome

Just delete it out of all groups so it won't show up on the portal.

Sorry, I don't use that app. Reach out to their support to see if they can provide that. 

Very good - so can you click on the Accept answer button above for me to close this one out? Thanks!

Okay, so go to the Users. Then search for the user you want and click on them to bring them up. Then under the product access, click the 3 dots to the right of the product you want to login as. Do you see Log in as user there?

Hi Vera, Go to Project Settings > Portal settings Click on the Portal groups tab. Remove the option for General group.

Hi Abhishek, The smart value syntax would be: {{issue.iM1Priority}} where that value is the EXACT name of the field (case matters). 

So, what steps are you actually doing? 

How did it get resolved? (for future readers)

So you checked the box, saved it, and then tried the process again, and it still didn't work? 

Click on Settings > User Management. Does what you see look like this? And if so, and you click on Managed accounts link, do you get a list of users? If so, you are using Managed accounts/users

Hi Nicolas, Are you using managed users? Can you log in as any other user?

Hi Mahmoud - Welcome to the Atlassian Community! You cannot use a number field in the Issue Statistics gadget because it has unlimited potential values. Therefore, you can only use fields that have defined sets of answers like dropdowns, radio buttons, user picker, etc.