John Funk Community Champion

1. Don't use Epic Link - use Parent 2. See number 1 :-)

Right before the status in add ( Then after SME") add this: SME") OR status = "Escalated to PT" and label = "update-given") AND Give that a try and see if it helps. 

Hi @Mikael Sandberg - Can you provide a screenshot of how to do that? Because I don't see a way to do it. I have changed the order of the issue links, but it always defaults to the alphabetical one first no matter what the order. 

I have never driven a motorcycle. Also wanted to learn, but never did. I have ridden on several in various parts of the world, but should learn to drive it myself. 

Hi Matt - Welcome to the Atlassian Community! No, you will not be able to modify the standard Jira screen interface to move the Comments section. You would need to contact the Smart Comments vendor directly for more information on whether the app will meet your needs. 

Hi Nabeela, The users need the ability to create issues on your project, so maybe the permission scheme changed. Take a look at that first. While in there use the Permission Helper just to verify for a user that can't see the form. Try both the Browse Projects permission and the Create issues permissions. 

Hi Inika - Welcome to the Atlassian Community! I don't think you are going to be able to adjust the Pie Chart gadget to have more than 10 slices. There might be some Marketplace apps that will allow you to do that. To change from Epics to Initiatives, just use a different Filter. 

Yes, that's what I would do. But what are all of those issue types associated with the Epic? It should probably just be the Epic issue type. 

Yes, Jack's suggestion is the route to go because you need to get the Resolutions all set in the single status before removing the other ones. The migration process probably won't allow you to set the Resolution field at the same time.

Hmm, surprised that version doesn't have the Parent field. So, yes, I would think you would go with the Epic Link field. Make sure the Epic Link field is on the Edit screen - that is most likely the error. 

Yes, it would look something like this:

Hi Marianna, If it gets escalated back to the other team, couldn't you just change out the labels? 

Hi Melissa - Welcome to the Atlassian Community! If you are wanting to just check off items on a list, then one of the Check list apps is probably the route to go. Or even just create a Checklist custom issue type field. If you want to actually create tasks for different people to do, assign them, set due date, track…

Hi Koutarou, Yes, you should be able to do that. Create your rule and add your lookupIssues action. Add your JQL that identifies the Done ones. Then you can create a variable if you want to go that route which would be the variable name and this code: {{lookupIssues.size|0}} Then you use the variable name for updating a…

Hi Jared, You might want to take a look at the Revyz Configuration Manager for Jira app in the Marketplace. You can do a free trial. It will let you do bulk deletes for the items you are wanting to clean up. Full transparency- I am an advisor for the app.…

Hi Elizabeth, If you do not hide your Done items, the board will get huge and unmanageable. If you are concerned that you won't be able to see your Done items, you can always to get them using the Search box or even create a filter or dashboard to show them. But leaving Done items on a Board forever is not a good practice. 

Hi Michelle - Welcome to the Atlassian Community! For the fields you are copying down values for from the parent, include code like: {{triggerIssue.Custom Field}} where Custom Field is the exact name of the field you are copying the value from. 

Hi Maria, Yes, you can do that. Not sure how "best practice" it is though. And it can get confusing to user who don't know what each filter actually does. But it is possible to do what you describe. 

Hi Ariel, You should be using the Parent field now instead of Epic Link.

I would open a support ticket with Atlassian to see why the content didn't get copied over. Please post back here with the resolution. https://support.atlassian.com/contact/#/

See if you can get a Free subscription to Jira Software (up to 10 users for Free). 

Okay - let us know how it goes here when you find out. 

Sorry assumed too much :-) Yes, start with an Issue Created trigger. Then add any Conditions so that it only does it for certain issues - what would that be? You can send that to me here, but you can continue to build while waiting for me. Next you add the Branch as above and then keep going with my recommendations above.…

Looks like some interesting apps. I have signed up!

Hi Nisha - Welcome to the Atlassian Community! One way might be to create an automation rule so that when an issue is closed, you check to see if the Assignee has any open issues that he/she is the assignee for (you could do this with lookupIssues function and size = 0). If so, then email you. Or you could create a…

For your last question - yes. Still create PROJECT-123, but then link it to PROJECT-124. That way if there is no PROJECT-124 and just PROJECT-125, then your process is not any different and you don't create a "fake" Epic just to have a filler link. Just my thoughts. :-)

Hi Petra, Is this a Team-managed project? After you create the Story, add a Branch for Most recently created issue. Then put the sub-tasks under there. Then add another Branch for Bug and do that same thing with those sub-tasks. 

Yes, you could do that through an Automation rule. Also, please reply inline with my answer so readers can follow the conversation better. :-)

Hi Iftikhar You don't unlock it. That's why it's locked. What are you trying to do with that field? It is not longer being used. 

Hi Patrik, Wow, there is a lot going on there. Yes, you can add a post function to clear the resolution and put that as the first step. Then add another post function to set the resolution and have it lower down in the steps. But the problem is that there is no guarantee that Jira will execute the steps in that order. I…