Hernan Halabi Community Champion

Then maybe you need a more complex solution not just a calendar. Have you checked big picture or portfolio to manage your epics?

@Alexander Bauer as far as I know, that's not possible to configure, specially on cloud. 

Hello @Jill mcnamee is JSD licensed? The knowledge base doesn't match with your description. I understand that you can't even create a service desk project at all

Hi again @Holly Leary you can't do that as you mention it but maybe you could create multiple calendars all based on the epic link. That way all issues associated to an epic have different colors than the others since you would assign a color to each calendar

Hi @Carlos Madriz could you add some screenshots to show what you see? Does this happen on any project or just one? I suppose that any other issue type within that same project you mention that it does work, correct?

glad to hear it. Please don't forget to mark this as solved ;)

anytime... let me know if that worked as expected

Hello @Holly Leary you might need to add some extra date and time custom fields. There is also the date custom field which is the one I suppose you are using and might be causing this behavior. I've used the others in team calendars several times and works fine to set time ranges.

You must click on the manage apps tab shown in the screen shot you sent

Hello @Tristan Swenson in order to delete an issue type, it mustn't be assigned to any issue type scheme. When you remove an issue type from one of those that is being used on a project, Jira will ask you to assign the existing issues associated to that issue type to another one that is valid for the project. Having said…

@[deleted] you can change the resolution from the edit screen if you add it there, yet is not recommended at all since it will cause you more trouble than any other thing. 

You got the second point right, regarding the first one you need to change it so it doesn't have a resolution. From the images you sent, that's not the case yet.

Hola @Angelica_Avila bienvenida a la comunidad. No es aquí donde debes solicitar esto sino al equipo de soporte de Atlassian support.atlassian.com si mal no recuerdo

The reason is that Jira keeps record of the previous keys so your old links continue to work. As an example let's say you click on an old issue you have on your email. It will have the old key, yet it will sent you to the ticket with the new key in place. Only deleting the project Jira will remove the key from its records

When dealing with automated systems it happens sometimes that you get loops as seems to be the case. Why? The system emails Jira Jira notifies the system about the new ticket The email triggers another notification from the system to Jira Jira reads this notification as a new ticket and the process starts all over again.…

URL should be something like this https://yourcompany.atlassian.net/plugins/servlet/ac/com.atlassian.jira.emcee/discover#!/discover It should be the first thing you see when you click the apps tab

@Adrian.neoenmeng.e in order to show on the backlog, the issue must not have a resolution at all. I would recommend you to leave the status without a resolution set in place and try to have a single ending point for your process. Like everything it ends at the closed status and when you reach that status you can pick one…

Hello @COO is this ticket coming from another tool? What do you have in the ticket content?

Hello @Ryan Buschert welcome to the community. Jira doesn't have that functionality as you describe it, yet there are two ways to achieve this. Option A you temporarily remove the notification scheme from the project (requires Jira administrators permissions). Option B, you change the ticket from the bulk change…

Hello @praseeda.sankarankutty in order to add zephyr, you must navigate to the apps tab from the admin menu. First thing you should see is a search box there from where you can search for zephyr and start a trial

hello @Roman Balakin welcome to the community, in order to have the key available you will need to delete the old project first.

Hello @Hari Sridharala if you can't see the bugs then either the board's filter is not including bugs, or maybe the status of the bugs isn't mapped to the board columns.

Hello @Alan Lindner even though the field isn't shown on the screen, it seems that it's marked as mandatory on the field configuration. You either have to make it optional there or add it to the screen. That would be the first thing to check. If the field is in the screen but doesn't have an asterisk, then the field is…

For dynamics fields you might want to check extension for Jira app. I know it has that functionality on the customer portal, haven't checked if it's the same for the agents view as well

Hi @Adrian.neoenmeng.e welcome to the community, cancelled issues won't appear in the backlog since those issues already have a resolution as can be seen in the last image you se

Hi @Shannon why not trying to use tabs on the screen? Each tab has a name that guides the agent what to fill on each request type. This might work as long as you don't have the same field on several request types or you will need to add the common ones on a single tab. The other option is that agents create tickets as if…

Hi @Joe F I suppose the fastest way to know if you had a reverse proxy is based on the URL you used for Jira. If you were using the default Jira ports 8080 or 8443 instead of the standard ones, then answer would be no. If you had something like Jira.yourcompany.com then the answer is ye

Hello, I try to avoid next gen projects since they don't have all the functionalities I have in classic projects. I would suggest migrating the project to a classic one

Hola @Luis_Marcel_Castañeda_Marroquin para reabrir un ticket debe haber una transición en el flujo de trabajo que te lo permita. Puedes agregarla si no está pero para eso deberás copiar el flujo, agregar la misma y luego reemplazar el viejo flujo por el nuevo en el esquema de flujos de trabajo. Cómo buena práctica,…

Hello @Praveena as @Bharath Kumar Kappala suggests, you can import the issues rather than the whole config. In my company we have done plenty of migrations from different tools into Jira and in most of the cases there is some data loss or the effort to bring the whole data requires a lot of effort and work hours that…