John Funk Community Champion

Hi @jviola The Parent Link field has been deprecated. You should just use the Parent field. So, the query would simply be: issuetype = Epic and parent is empty

Ciao Stefano, benvenuto nella community di Atlassian! No, non avrebbe senso. Se, ad esempio, hai inviato la stima originale a 5 e non hai completato alcun lavoro, la stima rimanente sarà 5, non 0 o un altro numero. E se la stima originale viene modificata in 0, anche la stima rimanente dovrebbe essere modificata in 0.

Hi @swangyal - Welcome to the Atlassian Community! This would be difficult to do somewhat as there might be multiple people put into the CC list. Maybe even multiple agents. So how would it know who to assign it to? So, a few things - the people in the CC list should be added to the Request Participants field…

Hi Swathi, Yes, what you describe above is possible for the most part if not all of what you ask. However, with there being External and Internal users with different needs and different Request Types, my opinion is that you should create a separate portal (Space) for each. However, you can hide request types from certain…

So sorry, just now realizing that you are on Data Center/Server. Automation for Jira would be an add-on. 

Hi David, Jira has implemented a standard Agile hierarchy for those work types. Story and Task sit at the same level. Sub-tasks can be either under a Story or under a Task. Estimation is not typically done at the Sub-task level - that's way down in the weeds. 

Hi Michael - Was the Epic in the same project/space? Or a different one? And if a different one, can you see other work items on that project/space? 

You are welcome

Hi @Krzysztof Borowiecki - This is an end user forum and no one here will have access to your audit logs. You need to create a support ticket with Atlassian here: https://support.atlassian.com/contact/#/

Okay, not sure what I am missing or what is the actual problem at this point of if there are several. Let' solve one at a time. What's your first hurdle that you can't do? 

Hey @Brian Ventura - Suggest you open a support ticket with the Refined vendor directly.

Hi Rita - Welcome to the Atlassian Community! Can you provide some screenshots so we have more context? Also, have you reviewed this guidance? https://support.atlassian.com/jira-service-management-cloud/docs/update-the-request-types-of-issues-using-atlassian-intelligence/

Hi @l.khutsishvili - Take a look at this other post for guidance. https://community.atlassian.com/forums/Jira-Service-Management/Hide-quot-Context-fields-quot/qaq-p/3202332

Hi Peri, This is an end user forum for Atlassian related products. We do not know who your Jira Admin is in your organization. You will need to contact others in your Org to find your Jira Admin. 

Hi @Support iCom Can you provide some additional information such as where this is happening, and what you are trying to do? 

Sorry, I forgot they moved the Shortcuts to the top menu. The users will need access to space (Browse Projects permission inside the Permission scheme) and will need to have the board filter shared with them if it is not already. 

@Erika Reategui - Did you try this? How did it go? 

Hi Antonia, As mentioned above, there is currently no way for a customer to update a ticket once it is submitted. So, you can go one of two ways in my opinion. 1. Add a Supervisor field to the form and have them populate it when the ticket is created - whether the value is needed later or not. It either needs to be a user…

Hi Ketan - Welcome to the Atlassian Community! Is this a Team-managed or Company-managed space? The easiest (and best) solution is to create a custom field called Email Address. It can just be a short text field. Then map the form field to the new custom field. Then your rule should work. Although you might want to add a…

I would think you would want to import into the Hardware Assets schema and not the Configuration schema.

Just create a shortcut and add it there - on the lefthand menu. And you are welcome. :-)

Hi Erika, You need to use an IF/ELSE condition instead of a regular Condition for checking the label. The way you have it now, if the Label is B, it gets to the first condition looking for Label A and when that is not met, it just stops. Put in an IF/ELSE condition with the first IF condition being the check on Condition A…

Hi Alex, In addition to @Marc -Devoteam- 's comments, you can implement issue/work item level security for the tickets so only certain Agents can see certain tickets. Those inputting requests for work (i.e. creating a ticket) will only see the tickets they submit. And they don't need a paid license to do that - just a free…

Hi Jens, A couple of things - if the project is not using SLAs at all, then you can delete the system default SLAs and hopefully that section will be gone. If you are on a screen, go to the Configure at the very bottom right of the screen and click on Configure. Then in the Context fields section drag the Development field…

Hi Rob, Below is an example of an automation rule I use to do the same thing. The field in common is Account Name. Also add any Conditions needed after the Trigger step. 

Great! Glad I could help. 

Okay, thanks for the update. Let me see if someone from Atlassian can come help you. 

This is an excellent app/tool! And one of those I was referring to earlier. 

To me, life is full of big wins in each of our lives. And the first one is probably buried way back in our childhood. They day you can dress yourself. The day you get to pick your own clothes to wear that day. Or the day you get your first apartment and move out of the childhood home, etc. My biggest was probably the day I…

Hi @PLaksh11 - Any update?