John Funk Community Champion

Hi Mario, One option might be to create an automation rule to move the ticket into another status after X days of the Resolved date. Then don't allow a transition to Reopen from that new status. And probably send an email to the customer that this ticket is no longer available to be reopened and a new ticket must be…

Maybe try a different browser or try with incognito mode. I suspect it's a browser thing. 

Hi Jose, No, that's not currently possible. The closest you could come to is to implement issue/work item level security which would hide tickets in general and specifically they would not show for that user in the queue either. 

Hi Geneviève - Welcome to the Atlassian Community! It is still separated on my screen - at least the inward and outward - blocks vs is blocked by. Those are separated. 

Hi cvanduyn, What status is the Scrum team using for their backlog? 

What type of field exactly is the field? 

Yes, but the Reporter gets added to that list and then the system can read off of that list and not two different fields. 

One level below Features is not sub-tasks. The validator specifically mentions sub-tasks, not Child tasks or children as Valerie pointed out above. So, yes, it would take a third party tool like JMWE or ScriptRunner to prevent that in the workflow. 

Hi Guillem, How did you archive them in the first place? Was that done while on a free trial of a Premium subscription? If so, you will not be able to move unarchive them unless you start another free trial for Premium (if it allows you to do that). 

Unfortunately I don't have those with me anymore - I believe my sons have them now if I remember. We had to purge a lot of things before our move to Dubai a few years ago, and we gave those things away to our sons. 

Hi Daniel, Short answer is yes, they disappear. In other words when you go to 30 seats you pay for 30 seats and not just 20 and get original 10 free. 

Totally missed that in the question. You are spot on. 

Hi Chris, You should probably open a support ticket with Atlassian for that to get an official answer. That seems like a critical thing. Please post back here with their answer for future readers (and I would love to know!). https://support.atlassian.com/contact/#/

Hi David, A couple of things - are all of those Statuses in the Done category of statuses (Green). Second, are you setting the Resolution field when work items move into those statuses (post function on the transition to the status in the workflow)?

Definitely a cup of something warm - hot chocolate, tea, hot cider, etc. And a nice warm Atlassian hoodie. :-)

Hi Sunny - Welcome to the Atlassian Community! Were you able to get this accomplished? 

Hi Rosalin - Welcome to the Atlassian Community! Jira does that with all fields that don't have a value. The only way to get rid of it is to make the field mandatory, which you don't want to do because then you would have to check it every time to save it. The other option would be to add Values of Yes and No with a No as…

Add the Linked Issues field to the fields when you do the Clone. Change the link type to what you want and the second part would be Trigger issue. 

Glad to hear you got it working. Please consider clicking on the Accept Answer button above so we can close this one out. Thanks!

Hi Scot, Unless you have an Enterprise license, I believe those existing instances will be created as completely different Orgs and total combined users are not considered, but just the users in each instance. So you get two independent bills. I suggest contacting Atlassian Support to get their take on it and see if you…

Hi Mariusz, The changeover should not affect Work Types that currently exist - in other words they would not be deleted. They are just work types that anyone can create with that name. My suspicion is that the templates and built-in workflows for that functionality will not be available for new projects created after the…

Hi Elsie, You should update the Request Participants field also with the value of the new Reporter and see if that solves it. 

Hi Collin, All you need is something simple like below where the Parent is the existing key of the parent you want to create the sub-task under. And yes, the terminology has changed to use work type instead of issue type and so on, but there is still a mixture of terms behinds the scenes in some places. 

Hey Colin - please create a new post with a new question so we can help your specific instance better. Thanks!

So, if the JQL is returning the right Sub-task, what id not working? It is not updating the Summary field as you expect? Can you share a screenshot with the details of the Edit to that field? 

Hi Pavan, Can you share a screenshot? 

Sorry, I updated it before seeing your reply. Glad it is working!!

And you are saying that using that Transition, it lets other Issue Types move to Done? Did you update the Workflow after making the change? Did you create the second transition yet? 

Okay so the first one is the parent that is getting selected in the lookupIssues, correct? And now you want to update the child Summary field value, is that correct? Or is there another field? And what is it you are wanting to update the field with? 

Hi Sérgio, You cannot do a Move using Automation in a simple way. The best you can do is Clone the issue in the desired target project, and then close or delete the original issue. So, there is no need to clone the issue into the same project, you can clone it with automation directly into the project where you want to…