Jack Brickey Expert

something like this.... project = xxx AND created >= startOfYear(120d) ORDER BY updated DESC, assignee ASC, status DESC

my only guess is that they are two different SW builds. The second image looks newer to me but have not observed in my instance.

I see. sure you can and should certainly expose the field on the View issue screen. My solution proposal is stating that you only need this field to be filled in by the user during the transition to Blocked so you need a specific screen attached to the transition to make that happen.

unfortunately not. agree this is a bit messy but that is what we have. you could consider a quick filter to help visualize on the fly.

so do you want issues to be included if "None" is in the Sprint or not? If you do then simply add the following to the above jql "OR Sprint is Empty" unless of course someone has create a Sprint called "None" (really bad idea) in which case you would add "OR Sprint is Empty OR Sprint = None"

i don't know what the Story screen is. i don't understand why you would want the blocked reason for anything other than transitioning to Blocked. I'm unsure if you still are having issues after the feed back from myself and Charlie.

I don't have an answer for you. You might reach out to Atlassian Support

To achieve the goal of requiring the blocked reason code here is what you need to do. Assumes you are NOT on NG project. * create a custom field for blocked reason code. Ideally this is a definitive list in which case you would use a select list (likely single select but maybe multi-select). If it isn't a definitive list…

FWIW i really don't like this approach as it is sort of an unlocked backdoor and if not careful could result in undesirable updates to issues. But that is just me. :-)

please go into board settings > general and click edit filter. view the results of the filter. do the issues show there? If not then the issues are 'falling thru the cracks' of your filter. Or rather the filter is excluding these issues. Inspect your filter. If the issues are being shown then if all statuses mapped as Nic…

sort of depends on the project type. but for classic projects this is defined by the status(es) you map to the backlog column. Example for a Kanban backlog... For Scrum boards the backlog is basically everything that isn't in an active sprint, though even the un-done will show on the backlog under the active sprint.

then let's debug... find an issue that isn't showing but is desired and interrogate against the JQL... * Is the resolution set? If not (unfortunate) then maybe change the resolution piece with "statuscategory = done" * What is showing in the Sprint field? If none then you would need to include "...or Sprint is empty"

thanks for sharing. good info for sure. though i have to say I don't quite get the value at least for my needs. certainly see where non-jira teams that are using Slack would be interested. will be interesting to see where integration w/ Jira goes over time.

not that I have ever seen.

yep. common problem and you will find many posts in the Community on this. as I mentioned above to correct do this... * edit the workflow * add a temporary transition from your done status back to itself called "fix-res" * add a post function to set the resolution on this new transition as desired * publish the workflow *…

Hi Adam, welcome to the Community. Assuming the issues were solved in a Sprint then the following might get you there... project = xxxx and assignee = fred and resolution is not Empty and Sprint not in openSprints() start w/ that and see if it needs tweaking. this assumes that Fred is the assignee for all issues he…

which gadget in particular? I tried the two dimensional in Safari and Chrome w/o issue. I suspect it is a bug in your instance and you should report to Atlassian Support. Let me know which gadget you see this on and I will try.

try this.... comment ~"2019 -2020" not sure if that will get you there but lets start there

I have not noticed this but haven't renamed in awhile. I just renamed one and have navigated away and back a few times and cannot reproduce. Can you reproduce at will? If so by what means? It is certainly reasonable to assume that there is a bug that has been introduced. Things like this have happened before in the every…

hmmm, don't think so. Are there any conditions unique to these transitions that you could rely upon. If so then you could still use the Transition trigger. TBH, I have never deployed a WF where multiple transitions exist between the same two statuses.

you can perform a full backup and download/store locally. Excerpt from docs.... To create a backup for cloud: * choose the cog > System * in the Import and Export section click Backup manager * under Backup for cloud select Create backup for cloud You can tick the include addition files option if you want to include…

You need to use Transition for changing the resolution not the Edit method. Depending on your exact goals this may include editing your current workflow, editing the transition within that workflow and including a post function to change the resolution field. Moreover, if this is a temporary cleanup exercise it may require…

I’m not sure what more info you need. How did you set up your current handler? Maybe I am misunderstanding your initial post where you indicated you set up an email handler for one project. Can you share how you did this?

Hi John, welcome to the Community. Have you attempted to set this up in Automation and running into an issue? If so please indicate where you are stuck. If you have not yet attempted I encourage you to do so. The Automation feature is pretty self-explanatory for the basic operations. In this case assuming you know who you…

Good point!

Have you specter the filter for the board to ensure they are not being hidden? Any quick filters coming into play?

Each project would need its own handler so that issues are open in the proper project. You simply repeat what you have done for the one project for others using a uniques email address.

It refers to any users listed in the “Watchers” field. You can see who is watching issues by clicking on the eye icon of any issue.

Hi Robin, welcome to the Community. If you are an admin - click on the Cog > User management > Jira service desk. Search for the user and click on the ellipses. This assumes the user is a Customer. If they are and agent or JSW user do this in the “Users” section under User management.