Jack Brickey Expert

when were the issues moved to Done. NG automatically removes Done issues after 14d in that status. You currently cannot change this in the default board. However, you can do the following: * Create a filter to represent your NG project, e.g. project = next-gen and save it and share as desired. * Create a new Kanban board…

@Dave Benson, welcome to the Community. The answer depends on more info TBH. Can you share more about what you mean by multiple IT teams? Are the customers different? Are the 'products' supported different? Some example thoughts... * If the agents (IT teams) are different AND the customers are different AND the type of…

I am familiar w/ both of Josh's recommendation and understand they are both very good. I personally use Automation for Jira and like it. Also Power Scripts is quite powerful as well. However, while I don't use Server it is my understanding that there is native automation so you should investigate if that is the case.

If the value for the field is deterministic such that automation could be used I would likely use an automation addon like Automation for Jira (but there are other addons to consider here for sure). However, if the value requires human thought then I might look at a workflow transition solution. Basically, create a…

@Luis Zuniga, welcome to the Community. I haven't attempted this but found this article that might be useful - https://developer.atlassian.com/server/jira/platform/creating-a-project-template/

@Edmondo, just an FYI that it is generally best to open a new question when there is an Accepted Answer. The reason for this is that your request will not receive the same visibility. Only those that have engaged on the existing question will be notified and even then if they have their notifications enabled to see new…

Sounds good. Let me know if you need any assistance.

do the automation logs convey anything? I assume you verified that the linked issue Resolution is indeed "Released"? Try to remove that condition just as a test and see if it works. If so then you know for sure that the resolution condition is the culprit.

@Phil W, OOTB while you can't construct a JQL that would reach thru the linked issue to find the status of the linked issue my alternative suggestion would be as follows... Use Automation to transition the JSD issue once the SW linked issue closes. If the status is unique, e.g. "Dev Complete" then you can easily search for…

Create a Dashboard and use the Two-dimensional gadget. Select “reporter” for y-axis and something like “assignee” or “status” for x-axis.

you can accomplish with an SLA and then use automation to transition the issue if the SLA expires. There is good documentation on setting up SLAs at Support.atlassian.com. Click on Service desk product and your version (cloud or server version) then search the documentation. Similarly you will find info on Automation…

Option 1 - Define a Quick filter for this under Board settings > quick filters Option 2 - define the overall board filter to exclude to do epics

What exactly are you seeing? Are you changing the SLA and then monitoring open issue with active SLAs or Closed issues with inactive SLAs? TBH, I’m trying to recall if SLAs are recalculated for Closed issues. For some reason I’m thinking they do not but I’m not where I can test that. are you on cloud or server?

There are any numbe of ways to accomplish this OOTB. Here are a few ideas to consider. * add a status to your workflow called say “Development” and place the JSD issue into that status when the link issue is added. This is precisely what I do. * add a label “dev” or similar * add a custom field to signify in development…

Unsure. You can check marketplace.atlassian.com and search there.

@Picme App, that is a long post. Are you referring to Chris’ comment or some other. Chris is referencing the use of sub-task to a story not task to a story. Regardless, this question is still open so if someone happens to have an answer counter to mine they can certainly post it here. Too you are free to post a new…

This is one of the downsides of labels and why I use them sparingly and carefully. I would recommend two alternatives. Use Components or a custom field for the teams and require the field when creating the issue. Personally I would use a custom field.

@Kim Dinh, can you speak to why you want to “copy”? The reason I ask is that if you simply are wanting to replicate a task and sub-tasks to facilitate recurring tasks you can use automation addon.

A quick thought/question, is it possible that the incoming has a different issuetype with different workflows necessitating a “move”?

It isn’t so much the number of filters as it is the number of concurrent queries that are run. With that said if you were to use a single filter and apply that to a dashboard then it would possibly result in better performance. However if 10 people run the same filter query at the same time it isn’t necessarily better than…

I don’t believe there are any default templates but it is easy to create. Adding gadgets is easy but you need to create filters and share them to use within the gadgets. 

If you don’t mind, when you get an answer please post here. 

Have you read this article?

@Andreas Aufmuth, I haven’t tried your specific use cases here rather I will offer my thoughts on options assuming that indeed Jira cannot natively provide what you are looking for. Disclaimer, this is not to say these will solve your exact needs but based on my experience and knowledge they may. * export to CSV and use…

@Christian Sprajc, regarding the automation to close issues after some period of time - there are a few other threads in the Community that answers this. One is just to the right under Related Content - “How to close ticket automatically ...”. You might start there. Regarding the author of the transition, IMO it is best to…

@philosurfer, I took a quick look at the doc but did not see where it was referencing NG projects. While it is illustrating “the new Jira UI” that is independent of “Next-gen”. Regardless, I’m quite sure time logging will be added in the near future. One last thing to mention here. Your reply here indicates “you” which…

Great! If this all helped please consider accepting the answer to close it out.

@Martin Hilton, thanks for the post. I haven’t actually tried this but interested. I looked at the other post and the JAC issue therein. I found it odd that the issue still shows as open even though your testing shows it resolved partially. You might want to add your observations to the issue. JSDCLOUD-5460

That certainly works. The “in” operator is used primarily used to shorten a JQL. For example: labels = “blocked” OR labels = “aaaa” OR labels = “bbbb” is more tedious than labels in (“blocked”, “aaaa”, “bbbb”)

you cannot. that option is for Classic projects only. at least at this time.