Petter Gonçalves Atlassian Team

Thank you a lot for your feedback, Scott. That's a really strange behavior that I was not aware of. So, the Epic panel displays properly in the issue detail view of the Issue navigator but not in the Epic itself when not signed-up for JIRA Software? I will talk with our internal teams to make sure that this is the expected…

Hello, Welcome to Atlassian Community! You must be estimating your stories with time tracking fields instead of Story points to display the information in the Burndown Chart. The field that should be selected to change the burndown Chart to display hours instead of Story Points is the Original Time Estimate: If it's not…

Thank you for your answer, Scotty. That's a really strange behavior since I am not been able to reproduce it, as I displayed to you in my last screenshots. That been said, I recommend you to open a ticket with Atlassian Support team so they can access your instance logs and better investigate what is causing this issue:…

Hello Nikki, Have you tried to import the exact CSV I described in my answer? Or you are trying to import a different CSV? If you are using a different CSV, can you please provide us with this? Additionally, are you trying to import that Epic to a Next-Gen Project or to a Classic project?

Hello Craig, Unfortunately, the new rendering of SLAs has not been deployed for JIRA Cloud yet, however, we've already requested this functionality with our development team: - Display lengthier SLA times in appropriate format (i.e. days) Please, vote and watch this feature request to increase its priority and also be…

Hello Andrey, Checking the error returned on your request type creation, I think that you have a custom field required that is currently blocking the REST API. Since it has not recognized the value "test" that you have tried to input, I think it is not a text field but maybe a field with pre-determined field options or…

Hello Neil, Indeed, the table markup is not properly rendering with the new issue view. We have reported this behavior as a bug to our development team: -Wiki Markup does not work in the New Jira Issue View Please, watch the reported bug to be aware of any new updates regarding this matter. For now, we recommend you to…

Hello Scott, As you can see in my screenshots below, I was not able to reproduce your issue. The Epic panel is appearing on both "Browse" and "Issues" sections: That been said, please provide us the following details so we can better troubleshoot your problem: - What is the browser you are currently using? What is its…

Hello David, Welcome to Atlassian Community! unfortunately, this automation feature is not available on JIRA Cloud, however, I was able to partially achieve your needs using the Automation forJIRA plugin. For your first request: an automation rule that will scan numeric customID field, and if there are any other tickets…

Hello Siva, I think JIRA does not have the functionality to copy field value to the parent when it's assigned, however, you can use JIRA Automation plugin to achieve it. Here's the rule: Please, let me know if this option works for you.

Hello Devon, Thank you very much for your answer. Analyzing the information you provided and digging a little bit further in our documentation, I was able to find out that indeed this search is not working as documented in this article. In fact, the search I've sent to you works because x is not a special character, just…

Hello Sunandha, Yes, the integrity checker can cause some slowness in your JIRA system, as you can see in the documentation I sent before. That been said, I recommend you to run integrity checker in a non-production time or in a time with less use of JIRA. Additionally, I'm currently checking the error you provided and…

Hello Björn, Unfortunately, it's not possible to filter issues only based on its last comment, however, you should be able to do it using the Script JQL Functions provided by the Scriptrunner plugin. The query would be simple: lastComment(comment query) You can check the documentation below for more details: LastComment…

Hello Devon, Welcome to Atlassian Community! As you can check in the documentation below, you can use \\ to escape special characters in a JQL search: - Search Syntax for Text Fields That been said, let's suppose you would like to find all the issues that are commented with the (x) icon. The query below should work for…

Hello Swaen, That's a really strange problem. I was not able to reproduce the same problem in my JIRA Cloud instance. For now, I would verify the following possibilities for the root cause: - Check if you don't have other custom fields (Manually created or created by a plugin) with the same name Story Point Estimate on the…

Hello Jeroen, Welcome to Atlassian community! The concept of Import projects on JIRA is the same for JIRA Software and JIRA Service Desk, there are no big differences between both process. In order to give you a more efficient answer to your question, please provide us with the following details: - Are there any existing…

Hello Sandeep, Welcome to Atlassian Community. Analyzing the scenario you described so far, I believe the best approach would be to create 1 issue per country as you mentioned since you are going to release the global requirement in several languages and their progress also will be registered in separated contexts.…

Hello Kim, Welcome to Atlassian Community. Can you confirm if you are using JIRA Cloud or Server application? I believe that this problem is related to your Browser configurations. Maybe you have a Google account already logged in your browser that does not have access to JIRA, however, once it is integrated by SAML, it…

Hello Sunandha, Once you reproduce the error again as suggested by @Ramaiah Pendli, can you please provide us the stack trace of the Error log so we can further investigate it too? Please, hide the particular information of your instance from the log, if there is any. Also, provide us with a screenshot of the post…

Hello Thomas, Welcome to Atlassian Community! I'm not sure if the Card colors query in board recognizes JQL parameters from plugins, however, you can try the following steps: - Install ScriptRunner plugin - Navigate to your board > Board settings > Card Colors > Select Queries - Write the following query for each category…

You are welcome, David. Thank you for sharing the workaround you've found to avoid the Single Sign-on! It will absolutely help other customers facing the same behavior. Have a nice day!

Hello David, The automatically sign-on happens probably because you are already logged with your work account (google) in your browser. Just like Youtube, Facebook, and other applications, Atlassian is integrated with Google Accounts by SAML and automatically use your first logged google account. That being said, you can…

Hello Lisa, Welcome to Atlassian Community! Per your description, you have created a custom field value where you add the Reporter's Supervisor on the ticket, however, you're not being able to find it in the Notification scheme of your project, is that correct? If that's the case, the field should be appearing in the User…

Hello Siva, Unfortunately, JIRA does not have a post function to achieve this, however, you can use the add-on Automation for JIRA. Basically, you would create a query using the Smart-value {{comment.body}} in the rule, just like in the screenshot below: Please, let me know if it works for you.

Hello Pawel, Once the Sprint historical data is not relevant to you, you can manually change the Sprint field value (By bulk operation) as described in the article below: How do I remove all Sprint related info from an issue Basically, you would perform the following steps: * Navigate to Administration >> Custom Field *…

Hello Ben, I would check the following: 1 - Check if the user that triggered the rule is, in fact, the customer of the issue. More specifically, check if the automation is not configured to be triggered as a different user: 2 - Check if the user does not have Service Desk Application access 3 - Try to re-index your JIRA to…

Hello Darapu, When you add the * parameter are you meaning that you are searching for issues containing the previous characters (AbcA0) or are the labels literally names as AbcA0*? To configure your issue filter to display issues that have only a specific label on it, you must use the not in parameter: labels = "AbcA0*"…

Indeed, I understand how this would be a pain point to have to manually change the automation everytime a request is approved, Johnathan. Unfortunately, JIRA does not have a feature to automatically configure the automation as you need. However, after some time testing and digging in the application, I was able to achieve…

Hello Johnathan, Thank you for the explanation. I suppose you have a custom field to identify the application that the customer is requiring in the ticket, is that correct? Or are they specifying the application in the description of the ticket itself? For the scenario you provided, I believe that you will need to make two…

Hello Benny, Welcome to Atlassian Community! I believe you are meaning the field drop-down in the basic view of the issue navigator, is that correct? Are you using JIRA Cloud or Server? If that's the case, once you specify the project and click to save the filter, the criteria will automatically remove the fields that are…