Petter Gonçalves Atlassian Team

Thank you for your confirmation, Janine. Also, I would like to suggest you try it in incognito mode or in a different browser, just to be sure you are not facing any cache problem. While you try it, I will check if I can reproduce this same behavior in my virtual machine (I'm using Mac) to have the exact same scenario as…

Hello Janine, Thank you for sharing the solution that worked for you. additionally, have you tried the workaround mentioned in the bug report? Here it is: - Click at the field and full select the value using (CTRL+A or COMMAND+A) and hit delete and enter. If it does not work for you, we will try to reproduce it with the…

You are welcome, Masaki. Have a nice day and let me know if you need anything else.

You are welcome, Chandana! Let us know if you have any questions on how to perform any of the steps provided.

Hello Masaki, Welcome to Atlassian community. The project which is not displaying the features you are expecting is a Next-gen project. The Next-gen project template was developed to provide a simpler and straight to the point tool for those customers who felt overwhelmed by all the classic JIRA features and its…

Hello Janine, Follow the steps below to properly delete your Due date: - Click in the due date field - It will display the calendar to select a date - Don't select any date, but click on the Delete/Backspace key to clear the date field - Although the date seems to be not cleared, it will be removed once you click out the…

Hello Joe, welcome to Atlassian Community! When you say "public visible", you mean to display the board for any external user which is not properly licensed to login and access your JIRA? If that's what you meant, it's not possible to display JIRA Software features like Boards to users that are not properly licensed, as…

Hello Bunyamin, The correct field that you can use to achieve your need is the Message Custom Field (for view). This field will not appear in the Create/Edit screen, but only in the view screen when configured with a valid value. Since the field can not be set in the Create/Edit screen, you must add a default value to it…

Hello Mark, Welcome to Atlassian community! Please, try the steps below in order to better identify what is different about this particular story: 1 - Did the Sub-tasks linked to this Story are also added with an Epic Link? Compare it with the other sub-tasks that are correct displaying under their stories. I think that…

Hello Chandana, Welcome to Atlassian Community. Per your description, It seems you are splitting your development tasks into smaller sub-tasks and configure a condition where the development task can only be transitioned when all its sub-tasks are finished. Have I understood it properly? If I have properly understood it,…

Hello Roberta, Could you please provide us a screenshot of where you are seeing the ESTIMATE field? Could you please also provide a screenshot of the screen/layout of where it is configured? The only thing I found related to what you mentioned is that the ORIGINAL ESTIMATE field is displayed in the Old issue view, while…

Hello Vishv, Welcome to Atlassian community. Since the board filter runs before the quick filtering query, if you remove the risk issue type from your board kanban/backlog you will not be able to return it in a quick filter. That been said, my suggestion would be to use the quick filter to do the opposite to have both…

Hello Melissa, I think that something similar to the functionality you want can be achieved by using the Two dimensional Filter Statistics gadget native of JIRA, however, I didn't find a way to return the % of tickets that breached/not breached the SL, Instead, It can be displayed in number. These would be the steps: 1 -…

Hello Rajkumar, Basically, you can follow the steps below to hide fields - Except for the issue security field, since it can be restricted through the permissions (Project settings > Permissions): - Navigate to project settings > Fields > Click in your field configuration > Fin the field and click to Hide The functionality…

Hello Tarang, The probability is low, however, I think it's worth to take a look at the Har file to check if any errors are returning. Since this a public channel, I recommend you to check the instructions I provided before and, if it doesn't help, create a new ticket with our standard support team:…

Hello Esther, Indeed, there are some limitations in the new view formatting, although we are still working to implement new features and make it better. Let us know if you still have any questions.

Hello Kailing, Just to confirm that we are on the same page: A request type is suitable for the email channel when both the Summary and Description fields are visible, and all the other visible fields, if any, are optional. If you want to use this request type, you need to change its setting to match the criteria. That…

Hello Joshua, Unfortunately, this option is not available for JIRA at this moment, however, we have requested our development team to allow the global deactivation of JIRA labs for JIRA Site Administrators: - Add possibility to disable the JIRA Labs features for all users on the instance and not per user profile That been…

Hello Chris, Can you please let us know what you mean by "SAS"? Is this any specification of your JIRA Server? What's the version of your application?

Hello Chris, Please, provide us with the following information so we can better troubleshoot your issue: - Are you using JIRA Server or Cloud? If it's JIRA Server, can you provide us with the version? - Are you able to perform the search when using the advanced option? project = Eligibility and issuetype = Story and Sprint…

Hello Andre, Welcome to Atlassian community! I have searched for similar errors and found some useful information that can help us better troubleshoot it. Let's try the steps below and check what results we got: 1 - Have you tried to reproduce the problem in a different browser? 2 - In a non-productive hour, try to disable…

Hello Angela, Unfortunately, JIRA Service desk does not have the ability to restrict the request type created based in a specific field of a customer or perform any kind of restriction for specific customers. We have created a feature request for this matter here: - User(s)/Group(s)/Roles security on creating certain…

Hello Schmitt, Welcome to Atlassian community! Per your description, there are only two possible things that might be causing your issue: 1 - The issue is not been properly configured with the resolution field when transitioning it to the last status. Doublecheck that you have configured the resolution field in the last…

Hello Shay, Unfortunately, it is now possible to display the time an issue has spent in status, however, there are some add-ons that can provide you with this information. That been said, you can use the Pivot by Statuses report provided by the Time Reports add-on to get this information: Let us know if this add-on would…

Hello Natasja, Unfortunately, our development team does not have a specific date to determine when this approach will be implemented, however, it is planned for the last quarter of 2019. Also, the fix should be implemented in the last version of JIRA Server and on JIRA cloud.

Hello Franklin, I think that you can use the Automation for JIRA add-on to automatically select the correct value in the group custom field depending on the group the user belongs to. Let me know if this option helps.

Olá Veronica, A sua regra parece estar corretamente ativada. A mesma nõ esta funcionando quando você transiciona a Story? Por favor, verifique no log details da automação se alguma informação é retornada.

Thanks for your answer, John. Please, let me know if the users have any other question I might be helping with. Have a nice week!

Thanks for your feedback, Claudio. Let us know if the problem happens again. Have a nice week! :)

You are welcome, Tina. Have a nice week!