Mohanraj Thangamuthu Atlassian Team

Thanks. This confirms that Issue hierarchy level of Features is '0' as well. Did you perform any re-name to issue types recently ?

Hello, Good day. Looks like your requirement is similar to the following feature request. https://jira.atlassian.com/browse/JRACLOUD-42197 Check if the workaround available in FR helps your need. Thanks!

Hello, Good day. Have you already explore the different customer fields available from Settings >> Issues >> Custom fields ? Attaching screenshot for reference.

Also from the screenshot I see a warning in the bottom of issue hierarchy page. Could you copy and paste the warning message.

Hello, Good day. From Settings >> Issues >> Issue types, do you still see the Features issues type ?

Hello, Good day. After selecting create an issue, you should have the option to change the issuetype. Attaching screenshots for reference.

Hello, Good day. Are you using Jira cloud or Jira server version ? If you are using Jira cloud then you can copy and paste the webhook URL from slack to Jira automation rule. Attaching screen shots for reference.

Or other option would be to re-create the consumer key entry that you are using.

If you are still facing issues, we might need to check on the DB level for previous entries. Please create a support ticket at https://support.atlassian.com/contact/

Hello, Good day. We would like to know if you have already reviewed the following link. https://confluence.atlassian.com/jirakb/smart-commits-performed-from-github-are-not-updating-jira-cloud-issues-as-expected-1206554375.html

Hello, Good day. Looks like your issue is related to this reported bug : https://jira.atlassian.com/browse/JSWCLOUD-26200

Please find latest updated on this thread : https://community.atlassian.com/t5/Automation-articles/Update-on-sending-Microsoft-Teams-messages-with-Atlassian/ba-p/2780258?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_article&utm_content=topic

Please find latest updated on this thread : https://community.atlassian.com/t5/Automation-articles/Update-on-sending-Microsoft-Teams-messages-with-Atlassian/ba-p/2780258?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_article&utm_content=topic

Hello, Good day. Is this Jira server setup or Jira cloud environment ?. Could you also attach the screenshot of the error that you are noticing ?

This looks correct. Have you tried creating new token to check the status ?. Also please give me the complete steps that you are following.

Hello, Good day. Please raise a ticket with our billing team at https://support.atlassian.com/contact/#/. Our billing team will be able to help you further. Thanks

Hello, Good day. Thanks for reporting the 'Typo', we will get this corrected. Thanks

Hello, Good day. Could you share the steps that you followed to create the API token.

Hello, Once the sprint is started it will show the bar on calender view. Attaching screenshot for reference.

Calendar view uses due date primarily. I understand that you want to show the active sprint issues on calender view. For now you can use the "Active sprint" tab.

Hello, Good day. You can use one of the following options, but both will require admin permission. 1. Create automation rule to send the webhook data 2. Create Webhook from Settings >> System >> Webhook.

Hello, Good day. I would like to know if you have already reviewed the following doc : https://docs.servicenow.com/bundle/washingtondc-it-asset-management/page/product/software-asset-management2/concept/integrate-with-jira.html

Hello, Good day. To confirm, when you create a new commit in Gitlab on specific Gitlab project then this is not shown on Jira issue ? On Gitlab project settings you can check the integration.

Hello, Good day. I would like to know if you have already enabled the view settings as given in the link : https://support.atlassian.com/jira-software-cloud/docs/manage-sprints-in-your-calendar/ ?

Hello, Good day. Following link has the list of supported ciphers : https://community.atlassian.com/t5/Jira-articles/Impact-of-updated-cipher-suites-on-Jira-and-Jira-Service/ba-p/2718998#M14758

Hello, Good day. Please post this query in JSM community as well : https://community.atlassian.com/t5/Jira-Service-Management/qa-p/jira-service-desk-questions

Hello, Good day. If you want to restrict few users from removing the links then you can restrict the "Edit issue" permission to only required users. Note : This also means users cannot edit any other field.

Hello, Good day. As we need to start checking your permission on Tempo side, create a ticket with Tempo support team at : https://marketplace.atlassian.com/apps/6572/timesheets-by-tempo-jira-time-tracking?tab=support&hosting=cloud to help with your permissions. Thanks

Hello, Good day. Have you already reviewed this article : https://confluence.atlassian.com/jirakb/team-field-is-not-visible-in-the-subtask-issue-view-screen-1316159527.html#:~:text=In%20Jira%20Cloud%2C%20a%20sub,can't%20edit%20the%20team. ?

Hello, Good day. You can use automation rule similar to : https://community.atlassian.com/t5/Jira-questions/Send-notifications-when-due-date-is-occuring/qaq-p/1822239 or You could also use filter subscription. https://support.atlassian.com/jira-software-cloud/docs/manage-filters/