Marc -Devoteam- Community Champion

HI @Jack Yang Regarding point 1, CLONE - is the default prefix when cloning an issue, this can be adjusted in the system settings. I rather would provide you with the option to create an issue in the other project and copy information from the original issue. Instead of the Clone action, use a create action and choose the…

Hi @Giga Shubitidze Welcome to the community. I expect this is an automation you are running. Can you provide the automation details for us community member to help you out. This will provide us with context and details.

Hi @Weronika Ociepka This can't be done. Permissions can only be doen via the permission scheme. Any issue type used in a project can be used by any user, if granted the create permission.

Hi @IYTHA RAJESH Hi If I quickly go over the documentation, there are limitations. "User Management Normalization Jira users, groups, and roles are an integral part of the Project Configuration - permissions, notifications, workflows, etc. Any users, groups, and roles used in the project that you are attempting to move…

Hi @[deleted] As stated in the documentation you linked. "Select the issue name and drag it up or down to reorder it. If the issue has child issues, they’ll remain with their parent issue. Your changes will be reflected in the board and list views as well." So child issues will follow their parent and so can't be…

HI @Balaji K M Please provide the community with the automation rule details (screenshots, etc) This will help community members to see what you currently have and try to achieve. P.S. In the email use the following option: <a href="{{issue.baseUrl}}.{{issue.key}}" >LINK</a>

Hi @Veronica As I'm looking at the options, the option is now renamed to Email. Choosing email gives you the options to email or still copy the link option. this link you can shre via chat or else.

Hi @Kevin Cocco As a source you should remove that specific project and create a filter for this project where you exclude the issues related to the label field. Save the filter and use the filter as a source in your plan.

Hi @Scott Mitchell Welcome to the community. Depending on the project types that your are using and related the permissions on the projects you should be able to use exiting tests in multiple projects. The issue you might encounter are: If you are using team-managed projects, these are containers and you can't use…

Hi @Jefferson Danilo Martins Fernandes Welcome to the community. Check the automation rules that are active on the project, a rule must trigger this. By default ootb setup this wil not happen

Hi @dwike_aprilia That can be done in the workflow as your 1st screenshot in your initial question or you can create an automation rule for this.

Hi @dwike_aprilia This is you screen, not the field configuration. Check the Field Configuration Scheme that is used on the project and then check the field configuration used by the field configuration scheme. And check the Resolution field if it's not set to hidden there.

Hi @Aslıhan Kara Welcome to the community. You could look at the issue layout on the project. But as @John Funk mentions, are you using different screens and how are th screens configured?

HI @e-Dongyang.Liu You could also use automation. You would need to field to store the C value. Have an automation trigger based on issue creation or field value change, then sum the values of fields A and B and store in C. Then re-fetch the issue date and have a condition to check the value of C against the required…

Hi @dwike_aprilia Can you check you field configuration and check if the resolution field is not set to hidden.

Hi @Patrick Keller Check the app documentation. there is loads of info how to create checklists via automation. Note: don't use the YAML field as its deprecated, use the checklist text option. Example: https://docs.herocoders.com/checklist/append-checklist-item-s-on-issue-transition 

Hi @Ken Isaacson A method to fix an error 431 include clearing the cookies.

Hi @Morgan Webber Reading other articles, I think you need to use the backlink feature See: Entry-links-and-two-way-relations Questions-and-Feedback-about-new-implementation-of-database 

Hi @Johan Pulles Welcome to the community. Only org, site or user admins are able to grant licenses (product access). See here how to mange user in the Atlassian user management, access you user management via admin.atlassian.com https://support.atlassian.com/jira-cloud-administration/docs/create-edit-and-delete-users/ 

Hi @Kevin Patterson , To be able to achieve this the field value needs to be represented in a custom field. All information represented in the description field is regarded as text, this doesn't matter if it is in a table or not. If this values in a custom field you can built an automation rule that based on the field…

Hi @Michael Leak Can you provide a screenshot of you workflow? And as @John Funk mentioned, what prevents you to create these transitions?

Hi @Denys Pidhornyi Welcome to the community. Do you have Atlas in your stack? Atlas is the management for goals, this is required, to enable the goals feature on a project.

Hi @Lara Sousa You need to use a company managed project. On team managed projects the board filter can't be adjusted, as it can only find issues from within the project.

Hi @Petar Cvetanovic Complete other option. Before the lookup, create a variable. Give the variable a name and use as smart value {{triggerIssue.key}} Then in your lookup perform the JQL as follows: issueLink = {{variable-name}} and issueLinkType = Timeline and "Start Date" is not empty Add a log action to log the result…

Hi @Amy Chamberlain No this can't be done. You can add the story points field to the screens and show that field on the cards on the kanban board. Even the ootb dashboard gadget can't achieve this, you would need a marketplace app to enhance dash boarding options.

Hi @Daniel In No this can't be done. There is no option to have documents shown on a form, you can have an attachment field, where user can add files.

Hi @Phil Bandy HAs the user been granted a license, or just simply been added to a project?

Hi @Petar Cvetanovic Then try the other JQL I provided: key = {{triggerissue.key}} and issueLinkType = Timeline and "Start Date" is not empty

Hi @Petar Cvetanovic Replace LinkType with issueLinkType. LinkType is an option from an app on my instance.

Best is to raise a support issue at Atlassian. https://support.atlassian.com/contact/