Petter Gonçalves Atlassian Team

Hello Hansika, I checked on a test instance that the Original Estimate field should appear with the same name in the validator selection and not as "Time" field as you mentioned, so I believe this can be the problem. That being said, I would first confirm if the "Time" field that you added the validator is indeed the same…

You are welcome, Allison. Please, feel free to accept my answer so this information can help other customers in the community. Cheers!

Hello Allison, 1 - The Activity Stream Gadget will display all the activity on your site since the beginning based on the filter you configured on it. 2 - No. The gadget will return all the information available on your site, however, once it achieves the Limit Display Options, it will be displayed with a tab Show…

Hello Paul, Unfortunately, there's a limitation on the filter that can be applied on Slack Integration. It can be configured by issue types and priority, but not for a specific issue-key. There is a feature request created to implement a JQL Filter to specify JIRA notifications sent to Slack channels, just like it was…

Hello Brianna, Unfortunately, History operators do not work for the field Project on JQL. It has been previously requested, however, our developers have decided not to pursue it: - History searches do not support the 'project' field That being said, The Assignee field is supported by history operators, so you can perform…

Hello Vitalij, This problem is usually caused by two possible reasons: 1 - The E-mail address of the user invited was not properly configured to receive e-mails when the invitation was sent. 2 - The Atlassian Cloud IPs or Domains can be blocked on your firewall, causing the invitation e-mail sent to be bounced on the…

Hello Brianna, The resolved date can be changed by import, however, the history of the cannot be changed. Here are the steps to perform it: - Export the issues (CSV format) which resolution was wrongly added after the change to status resolved - Get the data the issues were change to the status - Change the field resolved…

Hello Artemy, Checking on other similar cases, you will need to map those sub-tasks to a valid status in order to fix the problem. I suggest you try the integrity checker again only for the specific workflow section before trying the database update, flagging only a single option of the workflow section and performing…

Hello Lana, Usually, the behavior you are facing is because you have not mapped your Workflow Statuses in your Board columns yet. Please, navigate to your Backlog > Click on the three dots Icon (...) in the right-top of the page > Board settings > Columns and check if your statuses are properly mapped to your columns. If…

I'm glad to know I was able to help, Madhavi. Please, feel free to accept my answer to help other customers in the community with this same question.

Hello Madhavi, JIRA itself does not have this functionality, however, there is an add-on that can provide you the data to meet your requirement: JIRA Misc Workflow Extension Using the add-on, you can create a custom number field (with the initial value of 0) and use the post function Increase value of field to increase the…

Hello Neil, Unfortunately, there is no option to customize the fields displayed in the release detailed view, however, you have the option to click in View in Issue Navigator at the same page, where you are able to configure which fields you would like to display on the view. Please, let me know if this option helps.

Hello João, If you are not the Administrator of the user domain, only the own user can change his e-mail address by performing the steps below: - Navigate to https://id.atlassian.com > login with his credentials > Click on change e-mail option at the menu Email address and notifications If you would like to configure you…

Hello Lisa, To add new issue types to your project scheme, you can perform the following steps: - Navigate to your project > Project Settings > Issue Types - Click on Actions > Edit Issue Types > Drag and drop the issue types you would like to use on your Scheme Please, let me know if there is anything else we can help…

Hello Jack, In order to fill the required fields during a transition, you must add a screen to that transition and add the required fields to the screen. Here are the steps: - Navigate to your project > project settings > Workflows - Click to edit the workflow you are using for your issues - Click on Diagram > Click in the…

Hello Raj, Since Atlassian use a mix of our own IP addresses and others provided by third parties, you should also whitelist the other IPs of Amazon web services and CloudFront and CloudFlare as mentioned in the documentation below: https://confluence.atlassian.com/cloud/atlassian-cloud-ip-ranges-and-domains-744721662.html…

Hello Phil, Actually, the organization field is a locked field build to allow multiple customers on the same organization to share their tickets if they want too. In order to add more information as you need, you can create custom fields to have each detail you need in the request types and make them required. Please, let…

Hello Jeanne! Unfortunately, JIRA does not have this functionality, however, the create issue button can be clicked right away once an issue is resolved, so I'm not sure if this functionality would be worth implementing in the future. Additionally, here are some add-ons that can work for you in some ways: - Automation Lite…

Hello Dimitar, Unfortunately, validators are not being applied on JIRA Service Desk Portal when performing transitions, as you can see in the reported bug: https://jira.atlassian.com/browse/JSDCLOUD-4007 There is also a feature request opened for your specific requirement: https://jira.atlassian.com/browse/JSDCLOUD-4744…