John Funk Community Champion

No worries - that's what we are all here for!

All registered!! This will be my 3rd in person conference. 

Sorry, I should have thought of that the first time. Glad it worked!

Okay, let's go back to your original setup by removing the Branch. Move the edit up first before deleting the branch so you don't delete that too. Then try again. 

Let's try this in the summary: {{destinationissue.summary}} – {{issue.summary}}

Sorry about that. Here's the link: https://support.atlassian.com/contact/#/ Please post back here with the resolution so future readers of the post will know what happened. Good Luck!

Right - perfect!

Mine is usually when I am just sitting around with family or friends and reliving funny moments that have happened to us. 

Hi Dana, You need to check the Permission Scheme to see who has the Manage Sprints permission. It is usually best to give that to a Project Role like Scrum Master and then put the person in the Role. 

Hi Viktar - thank you, that's very helpful and brings clarity to the question. Are you clearing the Approval also? Or it was valid for the user to do the Approval and you just don't want them to see it any more? That would be strange if that's the case and Atlassian might not allow that. But if that's the case, the only…

What was your solution? 

Hi Mahboub - Welcome to the Atlassian Community! You cannot do that in any product in the Jira family. You can do Epic --> Standard Issue (like Story or Task) --> Sub-task But you cannot have a Sub-task of a Sub-task. So in your example - Make A = Epic, AA/AB = Story or Task, AAA/AAB/ABA = Sub-task

Hola Luis. ¡Bienvenido a la Comunidad de Atlassian! Desafortunadamente, no, no es posible cambiar ese texto.

Hi Vital - Welcome to the Atlassian Community! Are you sure the issue is in the last column on the board? Are there any open Sub-tasks under the issue? 

Can you share what you tried? And what didn't work with it?

That’s what I’m saying 😊 Did you try my suggestion?

Well, that weird. I know this sounds crazy, but have you tried logging out and back in again? Or on another browser? Do other users have the same problem? See if you can be added as an Administrator on the JWM project and then test it. Just trying to narrow down a few things. And if none of that helps, it's probably going…

Not sure you are going to be able to do it that way since it might not be the other issue that is the trigger issue. Maybe try adding a Branch to capture the linked issue before doing the Edit issue action. You would need to change the triggerIssue part as well. 

Hi Laura, Sure - you should be able to do that already. If the board won't let you move it independently, then just go into the issue and change the status to the next step in the workflow. 

See if you can see the Epic using a filter Just a simple filter like project = ABC and issuetype = Epic

Hi Heidi - Welcome to the Atlassian Community! Yes, you can do that. I just tested again in my instance and was able to do it. Make sure you have the right permissions in both projects to be able to see it. 

Hi @Björn Trier - Welcome to the Atlassian Community! You have to use the field name EXACTLY as it is create - case and spaces and all. I doubt your field is really EntryDate with no space, but it might be! The other thing is to use the custom field ID. Something like: {{issue.parent.customfield_10045.minusDays(7)}}

Yeah, I think you'll need to ask the project administrator for the same permissions. 

Sorry for not completely understanding your question. Maybe someone will be able to help you better. 

Hi William - Welcome to the Atlassian Community! Unfortunately, you can't currently add custom fields to the JSM notifications. Please see the feature request where you can vote for it and follow it. https://jira.atlassian.com/browse/JSDCLOUD-4642

Hi Joanna - Welcome to the Atlassian Community! How did you send the feedback in the first place? 

Hi Haseeb - Welcome to the Atlassian Community! What type of project are you using? Team-managed? Company-managed? Jira Work Management? 

They are different products. Jira Service Management projects are designed for things like help desks and support teams. Jira Software is designed for Development teams working on software. 

You are very welcome. :-)

Hi @Ivan Andrieiev Your query has (Status != Closed OR Status != Resolved) Since it is an OR, then it is correctly showing the 3 issues because the status is != Resolved for them. Try taking replacing everything inside the ( ) with Status not in (Closed, Resolved) So it would look Project = KVITIM and Status not in…