Hernan Halabi Community Champion

In order to see the field the users will have to have JSD licenses as well 

Pudiste resolver esto @Danilo Antonio Araujo Lopez ?

Claro, el problema es q no puedes decir eso a Jira tal como lo quieres. Si usas la aprobación de JSD solo puedes indicar 2 estados, si se aprueba o si no se aprueba el ticket, por ende en lo personal siempre lo mandaría a segunda aprobación y luego con alguna automatización, validar si el segundo aprobador esta vacio, y si…

and what do you have configured on the approval process of the esperando la aprobacion status? I can see you added the approval but there you need to define what happens when someone approves the ticket. I have the feeling the problem is happening there. Is the approval being done from the portal? We can continue in…

Each time you create a new project a new workflow will be created unless your new project is based on an existing project, I would suggest you to do that in order to avoid the extra workflows

Reach out me via LinkedIn or our website and we can talk more about your requirement and see how we can help you achieve it.

Groups configuration requires Jira Administrator permission, but if you use it for customers you can query for tickets reported by users that are part of a group instead of the organization. It's the alternative you have for your scenario

That's trickier, because users can pick who to share the ticket with, by default is the organization so a workaround would be with automation to clean the organization field each time the ticket is created and at the same time share it with your superuser. Maybe instead of organizations you should add the users to groups…

No, that isn't supported which is why I mentioned the add-on

You are correct, you need to projects and with the add-on mentioned before you can do one queue for both projects

I don't fully understand what you need to try to help you myself, anyway I'd suggest you to contact EazyBI support and ask them directly. They have good response time and they are really helpful in these cases

Sorry I was too sleepy yesterday today I recalled that on cloud we couldn't do that to one of our customers the way you describe, so we used all different projects but one single queue for the agents to make it easier for them by using this add-on. I hope is a valid solution for you as well

I know you can do that with extension for Jira add-on on the server version, I suggest you double check it's the same on cloud

Hi @Danilo Antonio Araujo Lopez if I got the idea right then yes you can. Check conditions configuration on the transitions. When ticket is at the first approval you already know the field value I understand, so you create two transitions, one to the second approval and one to the other step. Each transition will have a…

As an agent open the ticket and edit the organization field

If the ticket is shared with org A only those users will see it, you will have to share it with org D so they all can. Jira won't check if users share a common org. It just shows it to those that belong to the org that the ticket is shared with

The pricing should be visible at the marketplace. If you buy the licenses via partners you should be able to access to discounts. Contact us via our website if interested

Hi @Brent Carey we have customized the emails a lot with the https following add-on Https://marketplace.atlassian.com/apps/4977/email-this-issue It will allow you to do that and much more but it isn't the easiest to configure because of the features it has.

Not in the prettiest way but at least it's resolved

Even if you re-add them to the JSD project after assigning the JSW license?

That might be the case and that's why I wanted to see some screenshots of what Jira is showing you from the different views

Hola @salvador espinoza villegas te recomiendo que hagas un esquema de permisos donde nadie tenga permisos para ver el proyecto y con eso ya no aparecerá en proyecto en la vista de ningún usuario

If they have JSD license, they will always have the option to add comments to the customers, and only training can help you with that, you can restrict that from Jira. There is the contributor role as well, that in that case comments are always internal but there are some other limitations as well, maybe that's what you…

What @Damian Wodzinski would apply for all types of comments. @Rukmani I don't see many alternatives here. Why use JSD if you don't want to have interaction with the customer?

Hi @Rukmani you won't be able to do that, it's not supported

That's odd, if you search for the user in the user section does it appears only once? Maybe users are messing up and get duplicated (happened to us on server in the past). How does the user show at the JSD project before and after you add the license? And how does it show if after the license is added and you remove and…

As far as I can tell, the answer is no. Even if it would be possible, I wouldn't recommend it. There might be a magic file that allows you to customize this but on every update changes would be lost and you would be back on square one. I always try to avoid touching files from the installation directory.

@Jh what you want to do is possible but you are doing it in the wrong place. Field configuration applies for the field to be mandatory at any time. Instead, edit the workflow and in the close transition add a validator that components is required. Make sure to assign a screen as well where the user can set a value to it as…

@Kalindi Pathare organizations will be useful to manage access to the different environments but each instance is a separate thing. They won't see each other as one and won't be integration between them. There are apps that allow you to do different levels of integrations but they'll never be one. Question would be, why…

Go to projects, search for your project and click on the 3 dots at the right to later select project settings. That would take you to that view, if it's not the case, then you might be using a nextgen project and options will be different