Hernan Halabi Community Champion

I get it now @Albert Manuel , then as@Anton from HelloClerk_io mentioned as well. It's one invoice per instance and each invoice has details regarding the instance you are paying

Hello @Richard Sauseng welcome to the community. You can certainly do that you just need to create a query that brings all the issues from all projects and save it. Afterwards on the board configuration you place that query on it and that should be it. Here are the links to configure agile boards and how to get started…

Hello Patrick, you shouldn't have problems to use advanced roadmaps with JSM. When you start configuring the app it will ask what do you want to use as source of information. You could pick the JSM project there or maybe just a query that brings those long term tickets only which sounds a better option to me.

Hello @trypsin welcome to the community, you need to use issue security schemes for this. You will grant them access to the project using the permission scheme and then using the security schemes you will hide/show the issues that you want. Check the documentation to see how to configure it…

Hello @Albert Manuel what do you mean by 10 instances from the same account? What would be the account for you? From managing multiple invoices for our customers I can tell that each invoice does have the information of which url applies to. Even the email you receive should say it. The invoices would be one per instance.…

Hello @Sebastian Bissor I'm afraid you have a problem here since datacenter license applies for a single environment with as many clusters as you want but it's still one jira/confluence. You can't reuse the license for all the different companies instances

Hello @Francois Rheaume welcome to the community. The expedite swim line comes by default in new boards and it will show there the issues with the highest priority. You could configure the board to change that of you are the board administrator.

Hello @[deleted] welcome to the community. Check the app below. I'm pretty sure it's what you are looking for and more https://marketplace.atlassian.com/apps/1212161/extension-for-jira-service-management?hosting=cloud&tab=overview

True... my bad, too much multitasking. In those cases we have used in the past the following app https://marketplace.atlassian.com/apps/4977/email-this-issue?hosting=cloud&tab=overview It gives you more flexibility about who to notify when. This should allow you to ensure you don't notify the organization as part of the…

Customers involved would include the requested participants. as the documentation states.

Hi @Alejandra González it's the expected behavior. The way I see it is that it there aren't different request categories (in this case groups) why would I want to set a single category for the ones I have? The category is implicit since there is no other option. From the users perspective you would be adding one more click…

Hello @Ege Aktan - Inveon there were alternatives to do this in standalone versions but you won't be able to change this in cloud as far as I know.

Hello @Dan Allenby make sure the customer notification settings have the right recipients See link below https://support.atlassian.com/jira-service-management-cloud/docs/edit-the-content-of-your-customer-notifications/

Hola @Sistemas e Innovación Digital revisaría en una primera instancia lo que es el "issue detail view" (no recuerdo el nombre en castellano). Lo más probable es que allí este configurado que los campos estén ocultos y por eso no tienes información visible como agente. Si gustas comparte una impresión de pantalla de dicha…

Hi @Wasiq Dabir the tasks will remain in such column as long as they are added to the next sprint as well. The ticket status and its mapping within the board configuration is what defines in which column the ticket will show.

@mgl_support I just sent you an email about this hopping that we can help.

Hola @María Domene los contextos de los campos aplican a uno por proyecto. No podrás tener un contexto para un tipo de incidencia y otro distinto para otras incidencias dentro de un mismo proyecto. 

I suppose the None is a field option right? You should disable/delete that option. Jira already shows the None option that applies when the field is empty. By default jira tickets will be "none" (because fields are empty) and then the requirement at the field configuration level will work as desired forcing user to assign…

@Mohamed Kassim you can't do that, the only way would be starting a new project with that same configuration

Hi @Noa Masel you could try setting up the Service Request type mandatory at the field configuration level for the desired issue type. this way jira should ask for a value on that field when you are moving an issue to such issue type

Hello @Quin Church welcome to the community. You need to setup a permission scheme (ideally based on roles for better reuse and management). You might want to have 3 roles listed there. Internal staff, admins and customers. Set the permissions for each of them and apply the scheme to all projects along the groups into each…

de que tipo de calculo estamos hablando? operaciones matemáticas dentro de jira puede ser con la siguiente App https://marketplace.atlassian.com/apps/1214127/abacus-calculate-jira?hosting=cloud&tab=overview O bien con automation se puede hacer bastante que terminó siendo mi caso hace un tiempo atrás.

si, Córdoba sería el HQ. Puedes ponernos en el estadio Kempes que estariamos más por esa zona jeje. Así no tapamos el patio olmos 

Faltaría nuestra empresa entonces, somos de Córdoba también pero el equipo está todo remoto por argentina y México

Hola, aprovecho los minutos libres y va lo mío soy de y vivo en Córdoba Argentina. Siempre me llamó vivir en Alemania, creo que en esta instancia cualquier parte de ese país está bien para mí

Bienvenido a la comunidad @nicokaen un gusto encontrarte por acá. 

Without giving a lot of thought into it. I think you should be able to build something cool to do this within opsgenie that you already have the product with JSM. There might be drawbacks but it would keep the cost low

Hello @Andrei Tuch without apps to sync all the issues into one main project I can't think a way to do this. Nevertheless, why not have one JSM project for all instances and ask the user the instance he needs support at on the ticket? Optionally have one project per customer instance and then with this app you see them all…

Are you paying monthly or yearly? I suppose it's the second one so you might have to upgrade your users tier before adding more users

Hello @pgeorgiou welcome to the community, in order to hide them from the customers, you should make sure they aren't part of any group. See the documentation below about portal groups https://support.atlassian.com/jira-service-management-cloud/docs/organize-request-types-into-groups/