John Funk Community Champion

Hi Keith - Welcome to the Atlassian Community! Seems like you have already made up your mind without actually using it. Maybe you should give it a try to duplicate the things you do in your other tools and see where the deficiencies are. Yes, you can do the hierarchy structure you identify above. We are using that same…

Hi Krishna, What type of project is this? Team-managed? Company-managed? Jira Work Management? 

Hi Noa, One option is to create a new transition screen where the only field on the screen is the Description field. Then add a self looping transition (transition goes from X status to itself). Place the new screen on that transition. Then add a Condition so that only certain people can execute the transition (and thereby…

Oh yes - I remember pretty much all of these. Definitely the first phone I used was a rotary phone. And the long cord was never long enough. We had 3 phones in our house - one in the hallway, one in my parents' room, and one in the den/family room where the TV was. 

Hi Tim - Welcome to the Atlassian Community! Make sure the Not-doing status is in the far right (last) column (same for Completed). 

Hi Andres, I think I would create the rule based on the Field Value Changed trigger and use the Due Date field. Then add a Condition to check if the Due Date > startOfDay() and Due Date < endOfDay() To set the Due Date to the current date, just use now()

Very good - that should make it very easy. Can you share the screenshot of your rule now? And what is missing/not working with the rule? 

Hi @CTteam - Welcome to the Atlassian Community! You can use this for stuck in the Status for days: status = "In Progress" and status CHANGED to "In Progress" before "-3d" And this for not update in a given number of days: project = TLMC and updated < "-2d"

Yes, this was my point - multiple columns have been clicked on. 

Hi Steve, Not that I am aware of. We always just maintained the group manually. This is a request for what I think you want to do. You should vote for and follow it. https://jira.atlassian.com/browse/AUTO-1189

So, just stick the Summary field in the hidden with a generic text - New Issue, for example. Then use a custom field to gather the Summary information you want in the order you want. Then create an automation rule that fires when the issue is created to copy the value of the custom field to the Summary field.

Hi Kazim, I was getting that error yesterday as well. Is it still happening? 

Hi Sunil, Use Parent = ABC-123 where ABC-123 is the key of the Epic. 

Hi Ashley, What is not working with the post function? It looks like it is setup correctly. Does it fire and just not update the field? And, of course, another option is to use an automation rule. 

Hi Kyle, I would use a combination of the two project types. Leave your Sprint work in Jira Software and move your business related projects to Jira Work Management. One way to reduce the number of executions to a rule is to make the rule a schedule rule running once a day (or more during business hours if need be) instead…

Hi Ivy, I have not tried this before, but you maybe create a manual Automation Rule with a prompt for Sprint and then do a Clone Issue action using the value of the Sprint prompt for the Sprint field. 

Hi Braden, Did you rename the Epic issue type to Initiatives? Or some other name? Or what is the name of the Issue Type at Level 1? 

@Suresh - Any update here?

Agreed - a simple Condition should do the trick. 

That's weird because I don't see an entry for the Resolution getting set. What is the value that gets put in the Resolution field? This behavior with it not being in the history tends to lend itself to the the Resolution field being on the Create screen. Can you share the details of the Request Fulfillment Screen Scheme?

Hi Rocio- Welcome to the Atlassian Community! Please post your actual query so we can better diagnose. 

Hi Deb, You can create an automation rule based on a Field Value Changed trigger for the custom field. Add any Conditions if you need to. Then add a Branch for Linked Issues - identify the issue link type if you need to. Then under the Branch add an action for Edit Issue - choose the custom field. Then click the 3 dots to…

Hi Alicia, You say "We are using Jira v9.12.2" but this post says you are using Cloud. Which platform are you on? And can you share a screenshot of your actual rule? 

Hi Cash, Can you give is your exact scenario/use case? What would trigger the field to be updated, for example? 

I can't verify yet, but hearing that Atlassian will be backing off on this until September in an effort to implement a solution where the user will not have to be an admin. 

Hi Kristine, So why are you wanting to hide it and replace it with another field? Why not just use the Summary field? 

You might can do that by creating a variable and then using the variable in the JSON. 

I am hearing that this will be pushed out until September and that there will probably not be a restriction to just admins. 

So when you look at the history of the issue, who does it say Resolved the ticket? 

Can you be more specific as to which ones are not available?