Marc -Devoteam- Community Champion

Hi @Maarten Verreck I assume the JQL you provided is in the scheduled trigger then use a branch action for sub-task, then you can check sub-taks related to the trigger issues. Also if you want to email based on the sub-taks, it needs to be in the branch. An email action outside th branch is based on the main flow of the…

Hi @Florian Kleinig Welcome to the community. To keep it simple and based on my knowledge, you can still select which apps of the collection can be used by a single user. The collection has a set of apps, but, you can still set per user what their access on one of those apps is.

Hi @Mike Boutin Based on your description you will have to createca new custom field, based upon a multi-line field. In this field you can set a default. set this field on the create screen used by the TLE and remove the default Description field from the screen. Keep the default description field on the screen or screens…

Hi @gopal guna I think the answer on this is yes. But I think the best is to raise this with Atlassian Support (you nee to be an admin in your instance to raise requests). Otherwise your question could be answered in the Developer community. But based on your label that you are on a free subscription, you don't have rights…

Hi @BX This can indeed be seen in the feature menu in each JSM project in your instance.

Hi @Steven Vits As you are making a call to a Microsoft endpoint, this is providing the 401, not the automation rule in Jira. So the authorization towards MS not working. It also states this in the error "The provided authentication token is not valid, token signature is not properly formatted" Check what authorization is…

Hi @Asier Vadillo This sentence on the custom field relates to the context of the custom field. If you have a custom field related to a specific project and to clone an issue to another project, that is not set in the custom field context, this field will not be cloned. So to do what you want, you need to adjust the custom…

Hi @Georges El Haddad and @Jason Hills No this won't work with team-managed projects, as team-managed projects act as containers and a field created in a team-managed projects is only available to that project. You would need to create a custom field as Jira admin and set the field to be available global or to the related…

.

Hi @Madhuri Latha Bhumireddy The External Issue ID with number is a created field when an project import Every time this s done a field like this is created with a context to the specific imported project. "The current behaviour is that we save the value mapped to Issue ID as a custom field. This behaviour is intentional,…

Hi @Tobias Knittelfelder The mail message you get with subject "Issue due within 3 days." is not related to your personal notification settings, this is based upon a Jira filter with a subscription or an automation rule in the system that sends this email. If you are not able to see or access this, check this with your…

Hi @Rob Peters currently automation is not able to do this, neither are there options in the API. There is indeed the internal manual copy. Or you need to look into 3rd party solutions to copy a space or to bud templates to use.

Hi @N McMahon Welcome to the community. Only an Org or Site admin can remove apps. See this KB for the steps.

Hi @Ron Aisen Check if there are any proprties set on statuses in the workflow. This could be the case that attachments are prohibited

Hi @Abilash Yes, you could create a custom group picker field for this or use the Team field in case Teams have been setup. Team field can only contain a single option. Then the default Assignee field can be used so a single group or team member can bet set. You can base your queues in JSM based on the value of the group…

Hi @Vladislav Kruták First delete the whole organization, as you seem to be the last person in it and no apps are active. delete-your-organization And if you then want to delete your Atlassian Account, see this KB article

Hi @BARDIN Emilie You will need to adjust the request type within the project settings of the JSM project. See all documentation on request types in a JSM project, categorize-customer-requests-into-request-types 

Hi @Andreas Hausjell This is as intended in Cloud. You can't directly change the 2nd level. It has probably something to do in relation with the backed. You could reach out to Atlassian Support

hI @Louise Stallard Is the is a,managed account, is there a lock icon shown within the users details? Then this account has to be disabled or removed at the source, or you can remove the permissions of this user, then the user still has an Atlassian account, but no permissions to access the tooling.

Hi @Tobias Knittelfelder Can you clarify how you have setup this notification, is this based on an automation rule or filter subscription or based on the notification scheme? Can you provide these details and or screenshots, also are there updates done on the issue? What is shown in the issue history?

Hi @Ahlam Al Balushi As mentioned by @Nikola Perisic , you address is probably on a suppression list. Are you the Org admin of your instance, if not contact your admin to see if they can unblock you or you would need to raise a support ticket.

Hi @Steve Melzer Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request. This will help other community member trying to solve the same or provide them with a work around P.S. If the answer is very valuable to you, please share some kudos.

Hi @kafka max Have you checked if the screens contain the correct Story Point field, so not on the layout but on the screens itself. See the Screens option in the project settings, to see which screens are used and check it the field is on the screen or screens.

Hi @David Wilson Welcome to the community. Currently there is no option to do this. A link will only provide the page title.

Hi @kafka max Welcome to the community. Are team-managed projects also used in your instance, if yes there is a duplicate Story Point field. Choose the correct field. Is the field present on the screens used, so not just in the layout? Check the Estimation setting used on the board? Check if there is a context set for the…

Hi @David Washburn Information provided by @Samuel Gatica _ServiceRocket_ is very useful, but you can also lok at the public roadmap from Atlassian for released and coming features Roadmap 

Hi @Steve Melzer Could it be based on permissions within your slack domain? Maybe there are limitations there, as it seems the error is coming from Slack?

Hi @Andrew You could look into automation to have a rule based on issue creation, remove that information from the description field.

Hi @SARAVANAN BASKAR You can't, your intends/training phrases in your VA should line up with page titles or relevant information on pages in your KB.

Hi @Robert on a team managed project you can still adjust the workflow of a request type to you own wish. You just can't add a custom flow.