Jack Brickey Expert

You should add a sub-filter to your Kanban board, e.g. resolved >= -2w OR resolved IS EMPTY

OOTB organizational structure is not supported. I would suggest looking at the Marketplace for options to build this structure leveraging LDAP. If your org is very small you could manage this within JIra using Cascading field but that would quickly become unwieldy for an org of any size or one that frequently changes…

For my IT team we use JSD to manage issues but we use JSW for IT projects. We create a single Project for IT (PIT) and we use Epics for each project that will consist of many tasks or stories.

You can use JSD Automation and use “comment contains” function (example below). There is not an OOTB solution for having this available via an email link. There are addons like JEMH that would I believe.

You would use the Move function. If you look to the left under Recommendations you will see this article - Migrating-from-Classic-to-Next-gen-Software-Projects

This really comes down to preference and what works best for your team. You could create a literal workflow that has an “in test” status and either move to Done if it succeeds or Failed if not. The developer would then move back to In Progress and address the bug. The other method would be as you stated in #1 where a…

Excellent!

Good plan. You might try some other trigger coupled with the transition. I’m intrigued.

Well if the very same issue that you can manually transition succeeds on the automation alert yet fails on the automation transition and the automation is running under your user ID then something is certainly amiss.

So it seems that the automation is failing the transition. Here is something to try. See if you can take some action other than transition, e.g. alert a user. Just to see if it is failing the transition or any action.

Have you confirmed you can manually reopen the issue in question? In #2 above do you mean the “automation runs...”?

And don’t forget to also make the underlying filters shared.

Kari, have you found the answer as yet. It sure seems to be an automation to me. Can you share what automations you have in place? If there is a transition involved then I would suspect a post-function. Maybe you have an automation that is transitioning the issue and a post function is setting the resolution?

if you want to be able to hide/unhide these issue use a quick filter - "epic link" != "my epic link" If you want to never include on a board the ad the above into the board's filter

for anyone interested there are a number of open requests. Here is one that you might wish to watch/vote for - JRACLOUD-60841. You will note that it has been open since 2016. @jay modi as you are on server one free addon you may want to look at (no experience or affiliation on my part) - time-in-status-field

Not sure how to debug further from here. I recommend contacting Atlassian Support so they can log in and check things out.

Hi Jason, man this is consistently a hot topic. there is a lot of discussion around "time in status". In fact I was just on this thread earlier on the topic. I encourage you to start there and there is a link there to many other threads.

i would argue that how long an issue sits in a given state (duration) doesn't equate to actual time spent (effort). Using duration in status could be quite misleading. Simple example - i move an issue to In Progress and get started. Thirty min in I get side-tracked for two hours then I go to lunch (1h) and when I return I…

this is the best reference on the topic - export-more-than-1000-issues-to-excel-from-issue-navigator-in-jira-cloud

glad to help Tobbe! Best of luck and always come back to the Community for help.

Hi Jay. I'm guessing that you are looking for the 'age' of an issue where age = resolutiondate - createddate. Unfortunately this does not exist OOTB. Now if by "time spent" you mean the amount of time someone actually worked on the issue then use Time Logging feature.

Tobbe, I hope my answer makes sense here as I'm a bit confused by your question. First it is important to understand that issues do not belong to boards. Boards are simply a visual filter view of issues that are associated with one or more projects. What is displayed on the board is governed by the board's filter(s). Now…

let's dig a bit deeper. When you say you click on the project, where exactly are you doing that? Try this for me.... * click on Jira icon in sidebar top left then Projects * locate your project and click on the link * note results (i suspect it will be Open issues) * click on Backlog * repeat steps 1 and 2 * note results -…

@irene2 , first I wanted to convey that the Community here is primarily comprised of users like yourself though there are also partners and Atlassian members chiming in at times. You may have already known this. Also, any time you feel there is clearly a bug you should reach out to Atlassian Support. However, before I…

@newLab_Olivier , I have never experienced a queue not including all issue that are associated with the underlying filter. I would recommend scrutinizing your filter. Edit the queue, copy the JQL, go to advanced search for issues, paste it in and analyze the results. If the results are the same as the queue and you are not…

This is not yet available. There is an existing feature request for this for Jira Cloud - JRACLOUD-63150.

Give the user these project permissions: admin, browse and manage sprints. I would also make them Project lead.

thanks for checking on this Dario. I might be mistaken here as I don't use NG on a daily basis, but I seem to recall that you could see them either in the roadmap pane or the epic detailed sidebar. The ability to expand/collapse Epics in the roadmap pane is a nice feature.

please define "them" in "...can still see them." if you mean that customers that were in the org can still see older issues that were shared w/ the org then please check to see if the organization is still listed on those issues. While I have not tested this I suspect that just deleting the org does not remove it from…

Scriptrunner isn't required for the Validator solution as it is part of the WF as Radhika conveyed.