Hernan Halabi Community Champion

Hello @Raw Main removing a user isn't simple, pretty much nothing must be associated to it. You could deactivate it instead. Could you please tell the user directory order? That defines where Jira is going to look for the user first

Hello @[deleted] looks like the app doesn't meet the needs. I hope you are just with the trial if so. Anyway, if the app doesn't work for you, I'm afraid you won't be able to achieve this in cloud. There aren't other options in the market that I'm aware and to be honest I thought there were none when I started replying my…

That looks like the user can't be found at ldap rather than Jira. I suppose the user does exists there but maybe you are not bringing the whole directory. Just a subset of users in a group there?

Hello @[deleted] I believe you are looking for something like this https://marketplace.atlassian.com/apps/1219230/advanced-portal-reports-for-service-desk?hosting=cloud&tab=overview

Hello @Praveena if you are trying to use cloud, then there is nothing to download, you select the site url, fill some extra info and in a few minutes you should be up and running. Server and datacenter are the ones you have to download and install afterwards.

You should add the requested participants field on the request type screen, that way users can be added as part of the ticket creation

Hello @Raw Main did the user try to login? As the text of the image shows, the group isn't assigned until the user logs in and this might be the case here.

It would be from wherever you access jira on a daily basis. If it's reachable from internet, that would be the place. No need to add the obr from the UI of the server that runs jira. If you want to run it from the server... then most likely this is the link you need…

Great, don't forget to mark this as solved if it's the case.

See the attached images for guidance.

Jira core should come along with Jira Software license so I would focus on upgrading Jira Software only. The obr file should work if you install it from the UI, else you can stop jira, run the server installer and start jira again.

Top right of the screen. On the image you sent you can see it right next to the star icon

Hello @Marc_Müller you can't exclude those emails unless you setup your JSD project to allow tickets only from the customers you add to the project. If you can't do that because of the type of project and is a case where anyone is supposed to be able to create tickets you might want to setup an automation in Jira to auto…

Hello @Baskar_Ganapathy if the query is right and you are not seeing any issues it might be that you have unmapped status at the columns. Go to the board config and in there to the columns tab. If there are unmapped status you will see them on the right, move them to the right columns and that should do the trick. About…

Hello @Joe F if you are managing kanban and scrum boards then you should use the second one. Also if you go to the licensing tab you should see there which of the ones you are using.

Hello, by going to the board configuration and then selecting the quick filters you could customize them and make them based on labels

Not much that I can think of, can you validate at the db that the local groups aren't still listed there? Maybe they are even though you deleted them from the UI and that is causing conflict

Hello @johnathan_blanco Jira natively only supports one email per project. In order to have what you need you will need one of the following options * Two projects, one for each email * Two projects and see it's feasible to automatically move the issue to another project as gets created so all ends in one project (not very…

Hello @조현(영상) most likely the labels field isn't at the edit screen. Nevertheless if you press the l key on your keyboard or press the . (dot) and then type labels you should be able to edit the field. Clearly the most friendly option is to have the field in the edit screen

Hello @JAnderson it looks like a bug on your Jira environment. I use cloud and that functionality hasn't failed me. I would report this as a ticket to Atlassian because it's no the expected behavior

In theory yes but you can never know. What happens if you do that on a clean instance? 

I don't have many ideas of why would it be, but I'll have to ask. After the sync, did you log in with a user that belongs to those groups? Maybe they aren't created just because of that. Similar to what happens if by default you assign a group to the ad users. The group isn't assigned before the first login.

@Paul Salcombe even though it's a next gen project, you still choose who can see the project, and it doesn't matter if you are the admin. The automation rule might be configured to be run as another user which isn't listed in the project

Hello, Check the workflow validators, sounds like there is a permission validator that your user doesn't pass it.

Excelente, no olvides marcar esto como resuelto si es el caso. Saludos

Hello @Warren Goldman on the paid version both fields might be using the same set of screens and workflow. Try the move option instead and you should be able to change the issue type.

Hi @Marina Perez send some print screens to better understand what you are trying to do and when it's failing. Application links are usually simple if there are no firewall rules making the tools invisible to each other Also, if you are on cloud the tools should be already linked to each other

Hola @daniela_suarez revisa el siguiente enlace https://confluence.atlassian.com/adminjiracloud/workflow-properties-776636709.html Dentro del Estado final deberías poner la propiedad jira.permission.work.denied y debería de resolver tu necesidad

Hello @Paul Salcombe you should check which user is supposed to run the automation rule. Jira is complaining about that user. Either change it or grant it permissions to the project.

Last time I checked to have that integration you must have access, it can't be done straight from Jira. Maybe you need to add the user there first, it's not the tool I use the most.