Hernan Halabi Community Champion

Hello @Mukul Singla welcome to the community,can you share a screenshot with what you see?

Hello @MT welcome to the community, you can just hide the bar on the left, you can change the highlighted borders

You could use the Automation module to auto add either a participant or an organization. Don't fully recall the options so depending on what you have the hardcoded or not that needs to be the solution

Hello @Ronald Spina welcome to the community. Customers can share their tickets with other members and with organizations as well which would be a group of users of needed

Hello @Philip Jurke welcome to the community. As far as I can tell, you can't do that with Jira native functionalities and don't know any apps to do it. You would have to develop a service that talks with Jira via rest API and do the math of the amount of tickets over there 

Hello @Tom if you have Jira software you can create a kanban board that shows both projects. Boards show whatever you use in the query. I use that with some of my projects as well. It allows you to see things in one place but you won't be able to see all features from service desk without fully opening the ticket, SLAs…

Hello @Marina Arratibel Ávarez welcome to the community. Don't hesitate asking whenever you need it. There is plenty of people here willing to help

En el error menciona lexorank, recuerdo que en la solapa de sistema hay una opción relacionada a eso, no recuerdo si tiene opciones adentro para solucionar problemas relacionados a eso. Revisa allí también por las dudas

As far as I know a comment applies as an update. You can easily validate that on a query in which you can show that value on a column. Make a comment to one of the tickets if the query result and see if that value changes as well

Hola @jvalencia el error parece estar relacionado con el módulo de agile. Que ocurre si reindexas o bien pruebas correr un integrity checker? Podrías estar relacionado con caché o algún valor erróneo en la base de datos

Hola @Mariperla Macias bienvenida a la comunidad, no dudes en consultar cuando necesites algo.

Hello @[deleted] unfortunately you can't change that.

You mean that the whole Jira interface disappears? Or what part of blank? What do the logs say when you click there?

Hola @jsaezg bienvenido a la comunidad, no puedes borrar las etiquetas desde la interfaz web. Posiblemente puedas hacerlo a nivel base de datos pero no sería poco recomendable. De todas formas no puedes evitar que justo después del cambio un usuario vuelva a recrear una de las etiquetas borradas

Have you checked the logs? Can you send some print screens?

You can either create a new board or replace the filter of an existing one in order to change the visibility of the filter and impact only on the desired boards

Hello @Darren Ganasen that shouldn't happen. Automation errors are logged within that module, not shown in the UI

After trial expires you can't create new tickets

Hello @Lubna Malik the thing is that as the first rule is executed, the update date changes to that same moment, so the ticket never has an updated date bigger than 2 days. You could setup slas for 2,4 and 7 days and use those as triggers each time one of them expires

hello @Malin Svensson welcome to the community. If you restrict the visibility of the boards queries you will be able to decide what will you show to the customer. Anyway keep in mind that in order to see the tickets within the board they will need access to the whole Jira project. If the project contains info from other…

Hello @mohamedelsayed kamel welcome to the community, Jira only has a free version for cloud services, the on premises are all paid versions

Hello, has a reindex been done? After upgrades or migrations you usually need it. It is also recommended to run an integrity check

Try to avoid next gen projects. There are many features missing that you will need along the road.

Hello @larias that means the ticket doesn't have a resolution in place. Make sure that there is a value assigned to the Resolution field, once you have that, no matter the status of the issue, you will see it with the line through

If the field is unchecked from all screens, means that it's not in any of them. Go to the project configuration and the the screens tab. You will have at least one screen scheme there. Select it and it should show you one to 3 screens associated to it. Open them and add the field you created. Repeat the steps for all the…

Hello @Deepak Verma you could do that with the Automation module. Trigger could be when an issue is transitioned and you can later filter for that specific transition. Then, with an if condition you evaluate the field value and based on that assign the ticket to someone else

Hi @PavelKarpenka you can only replicate them. So I would suggest you document your previous reports and just create a new board with the same configuration

@Francisco Totesaut esa barra es en la vista vieja de jira cloud. Las nuevas instancias tiene la barra superior que en mí experiencia es más cómoda que la lateral

Hello @Manuel Plaza that won't be an easy task. You need to pick 1 instance to be the final one. On it you must import every project you want to keep by doing project imports. These imply you have previously replicated the workflows fields and options for each of them. Once the merge of all the instances is done, then I…

Hello @Irene_Jiménez you should do a query for the type of issues you want to export and from the search view you will have the option to export as CSV. You can export all fields or just the ones you configure in the search view