Marc -Devoteam- Community Champion

Hi @Roxanne Francis As @Lisa Forstberg mentions, set this in the JQL in the scheduled trigger. At the bottom of the scheduled trigger, there is this option: "Run a JQL search and execute actions for each issue in the query"

HI @Heide Behrens Yes this is correct on the free tier permissions are not accessible.

Hi @Mårten Woxberg I hope one of these KB articles can help you out. * https://confluence.atlassian.com/confkb/error-rendering-webpanel-no-renderer-found-for-resource-type-300814261.html * https://confluence.atlassian.com/jirakb/error-rendering-webpanel-1333331815.html 

Hi @Rob Horan It shouldn't be. I suggest to contact Atlassian Support on this license/billing issue.

Hi @Gor Greyan This can't be done. Links between issues in different instances can be set, but that's all. Actions on links issue, or JQL related to linked issues from other instances is not possible.

Hi @Harvey Tong Welcome to the community. I'm not familiar with this integration yet. You could look at the automation trigger "Vulnerability" found and based on the severity. Then add conditions and actions as in a normal automation rule.

Hi @Steven Becherer I quickly checked the documentation of the vendor. Did you follow their Lcoud migration plan; Migrating+from+Dataplane+Server+Data+Center+to+Dashboard+Hub+Pro+Cloud If so and you still have warnings or issues, I recommend you to reach out to the vendor and ask them to provide guidence. They should know…

我無法重現您在實例上遇到的問題。 我仍然有合併選項 我還嘗試了另一個實例，一切似乎都按預期工作。 它是否是一個舊頁面，仍然使用舊編輯器製作，如果是，請更改頁面。 請參閱此知識庫文章：https://support.atlassian.com/confluence-cloud/docs/convert-pages-to-the-new-editor/ 如果這不是問題，請聯絡 Atlassian 支持 https://support.atlassian.com/contact/ 

Hi @Logistics1520 Check your logs. They should provide information.

Hi @Anders Ottosson Welcome to the community. As @John Funk mentions share your rule. But if Acceptance Criteria is a field in the subtasks, you can set this field with content on creation of the issue. Just state the information in the field when creating the subtasks.

Hi @Samuel Kolloch By direct link is meant. https://<your-instance-name>.atlassian.net/browser/<issue-key> This is the only way to see issues from archived projects.

Pleas accept my answer as the solution to this question.

Hi @Yaniv If the app doesn't offer these function, then it can't be done. Reach out to the vendor and see if they migth have a solution. If they have, please share it on the community.

Hi @a855031 Then the option would be to change the name of you custom field. Slashes are always bad news in a name, they are usually revered in an application.

Hi @Jessica Oveys Even setting the Epic Status to Done and all child issues to Done its still visible. I agree with @Trudy P Claspill I voted as well.

Hi @Yaniv Are you using an app for testing, if so what app? Also I would refer you to read the apps documentation, as not al apps offer JQL integrations and you can only use the apps functions to view test related information

Hi @Eric Bailey When you delete the value, its gone from the system and you can search for this value anymore. If you disable the option, the information will remain in the system and will be searchable

And you are probably running in to the following limitations on team managed project in relation to automation; https://support.atlassian.com/cloud-automation/docs/limitations-in-team-managed-projects-for-automation-rules/ 

Hi @Kurtis It might this KB article will help you: https://support.atlassian.com/jira-service-management-cloud/docs/add-an-approval-to-a-request-type-in-team-managed-projects/ As I think the normal approver and approval are only used by Company managed project

Hi @Ridha B. Are you the org or site admin, of not contact them and let them check your access. https://support.atlassian.com/contact/

Hi @Daryna Kaloshyna Check under connected apps and if the app is stated there remove the app.

Hi @Igor Titov What is associated with the field? It will impacted filters, workflow options, automations, used in apps that are installed, like scripts, where the exact name of the field is used. If the ID of the field is used it will all continue to work. Could you test it in your sandbox?

Hi @Daryna Kaloshyna Are you referring to an app you installed accidentally on sandbox? Just install the app on the main instance and you can use it there. Or am I completely wrong in my assumption?

Hi @Melody Josey You can use the audit feature build in in Confluence, or you can look at marketplace apps like; reporting-for-confluence 

Hi @Eunsu Kim Welcome to the community. I would suggest that you reach out to Atlassian Support on this issue on your instance. First could you try a different browser and/or clear all history and cookies on your current browser and try again.

Hi @Heide Behrens Welcome to the community. * If you don't use page restriction every page in a space is available to any user who has access to the space, based on their permissions they can only view, or create and edit. * Yes page can be given restrictions, based on user or group. You can grant view or edit permissions.…

Hi @Igor Titov The smart value changelog want to use the name of the field which in your case would be: {{changelog.Due Date}} It might be conflicting due to the fact the custom field with id 10030 has the same name as the ootb field. Could you rename the field an test if it will work?

Hi @Boyan Iliev Within Jira and Confluence in the settings, use the option application links. I would not disconnect Confluence in Jira as you are not able to use Jira information on Confluence pages anymore and can't use inline links to Confluence in Jira anymore.

Hi @Jill Vieregge Check the app that is used for smart checklist and review the documentation. A good option is to contact the app support and ask them if this is normal behaviour, or that this occurs due to someone creating a checklist template, or using specific app options.

Hi @Ashbeel Ashkar Gohar Check the differences in the permission schemes. Are the schemes based on project roles, groups or users. Browse is the most important permission, if no browse permissions are granted, the other permissions don't matter. Browse is required to see issues in the project