Jack Brickey Expert

It could be that you are using the “Issues” view in a project? If so then you can edit the JQL to use a DESC rather than ASC. I am referring to the screen where you do an advanced search. I suspect that in time Atlassian will add sortable column headers to the view you’re looking at.

You can simply click on the header of any search results to sort by the column and order ASC or DESC

I have not seen this in the past. Is it possible that some issues were deleted that had that label. This might explain why you're seeing the behavior.

this is not possible OOTB. You might check the marketplace for Apps.

what or who is DEQ Jira? That sure seems like automation. Are you sure you checked legacy automation as well?

so if for example you have a label named "tested" and you search for any issues with that label using this query - labels = tested then nothing is returned but if you edit an issue and start typing "tes" then "tested" appears?

Where is your second image taken from? Can you share your entire screen so I have a better idea?

Here is one thing you could do - use this JQL labels is not empty to find all issues that have a label. Export this list, I recommend removing as many columns as possible if you have a large database. Then use excel formulas such as pivot table to find up every unique label. Not glamorous but it will work.

Hi Robyn, Can you please share a screenshot of what is in your permission scheme for delete issues. Project settings > permissions - Delete issues One final note - I strongly recommend not providing individuals with delete permissions. Deleting issues cannot be undone and invariably something will get deleted and you will…

First I suspect that your dashboard is including issues with statuses beyond whitcher board is showing. This would explain discrepancy between the numbers. One quick test to validate that would be to use a two dimensional gadget on your dashboard for the X axis choose status for the Y axis choose maybe issuetype. It's in…

I definitely suggest reaching out to Atlassian support. Report back if you get resolution. 

You might find this useful - https://support.atlassian.com/jira-software-cloud/docs/how-do-jira-permissions-work/ 

If you suspect the same issue then yes I would definitely reach out to Atlassian support. 

It is not possible to achieve your goal as stated at least out of the box. However I wonder if a cascading field might meet your needs?

What do you mean by specific type of request? Keep in mind that automation is after-the-fact so the issue will have already been created in the JSM project so redirecting the create request is not possible. If I miss understanding your question please re-elaborate. 

Unfortunately I cannot check anything from where I’m sitting. I am just a user like yourself. This is not Atlassian Support but rather a community forum. with that said you likely don’t need a lasting support to solve this issue. Did you check the other things I suggested? Can you give me more information about the type of…

is this a CMP or TMP project? can you check your personal settings - avatar > personal settings ... email notifications if CMP - check project settings > notifications to assess if you are in the associated roles that will receive notifications 

And if you happen to be using team manage projects it's a simple as a feature toggle under project settings.

hi Alla, I see that you were on the free platform. Portfolio previously was a separate Application but now part of premium subscription. With that said, you indicate you're trying to change from kanban to scrum. Assuming that is your singular goal, you can create a new scrum board in your free version to replace your…

Hi @Andrés Laplace Kellogg , I have never observe this previously. I wonder if you could be some kind of automation going on your instance? In any event regarding a fix, should there be an actual bug, should be directed to Atlassian Support.

It seems like you have created three separate instances rather than install the applications on a single instance. As you were on free I am on sure what the process would be to get this resolved. You might reach out to Atlassian Support and select the billing option for their advise.

Lamentablemente, no puede solicitar campos con solicitudes de correo electrónico, a excepción del resumen y la descripción, que equivalen al asunto y al cuerpo del correo electrónico. por lo que, en última instancia, una solución automatizada está muy sujeta a errores humanos.

Con el canal de correo electrónico JSM no puede especificar dinámicamente el tipo de problema o más bien el tipo de solicitud. Todas las solicitudes de correo electrónico vienen como un tipo de solicitud específico. Podría considerar usar la automatización para actualizar el tipo de solicitud según el cuerpo o el resumen…

No that is actually good. If you did find resolution there it would mean someone created a custom field with the same name as the system field, which is not a good thing. however at this point I’m at a loss as to why you would not see the resolution field in the transition screen. Without actually seeing it firsthand I’m…

This is not currently possible. Here is an open suggestion - JRACLOUD-72007 

Is this a software project? Note that often a board’s columns don’t map one to one to a workflow. Rather many users choose to combine several statuses into a single column. For example , all in progress statuses into a single column. Of course others do you want a one to one relationship which is also perfectly fine.

Ah…So please understand that your board columns are not directly associated to your workflow. Columns in your board can be different but you map your workflow statuses to the columns. This is done under board settings > columns. Click on the ellipses in the upper right of your board. finally, if you are using a business…

Go to any project’s Project settings > Automation then click on Global configuration link at the top. In this screen click on All rules. This will present all current rules EXCEPT Legacy rules which can be found under each JSM project’s project settings > automation > Legacy Automation.

I really couldn’t say. You might check on Jira.atlassian.com and see if there is already a suggestion (likely I suspect) and vote/watch. you might consider some other work around using dates like this… sprint not in opensprints() and resolutiondate <= startofweek() and resolutiondate > startofweek(-2w) of course the…

Yes that was my understanding as well. I just haven’t tested in a long time and was hoping that maybe the feature had been added but apparently not.