Marc -Devoteam- Community Champion

Hi @Rahul As @Rilwan Ahmed stated a Custom Field of the type cascading select can help. This field has 2 levels only if you require more the following FREE marketplace app can provide a multi level cascaded drop down.…

Hi @Achmad Rifki You can achieve this by filtering on status category The other option is to exclude them in your board filter. As the time line view is also related to the filter used in the board.

Hi @Akio Senda Welcome to the community. Are you using the default Jira gadget on the dashboard, or are they provided by an app. What is your requirement for the chart? You could simply adjust the filter used or not show components on the chart. More information could help providing or helping you to a solution.

Hi @Collista Lewingdon What subscription of Cloud do you have on a standard I also have the field team, this is related to the teams you can setup in the Teams section in the toolbar. The Team field I and Sari are referring to is related to Jira Advanced Roadmap, this requires a premium cloud subscription. The Team field…

Glad to help. Please accept my answer.

Hi @Dan McLean You can only prevent this by removing the Story Point field from the edit screen. This will mean you can't edit the field in any status. A work around can be to add transition on status backlog. this transition will go from status backlog to status backlog, put a screen on the transition with the Story Point…

Hi @Legend Jones This is not possible as this information is stored in the system. Status change history is also available via JQL.

Hi @Rebekah Myers I got it working on option id as well, if you quote the option. If you don't put the id number in quotes, it will fail. "customfield_10080" : [ { "id": "10112" } ] Assuming 10112 is the id of the value you want to set.

Hi @Lorenz Scheller Then reach out to your Jira admin, to see of the app has permission settings. That could be a reason why others can't even see or use the options provided by the app. Does the app have options that only certain user can use and view these functions?

Hi @Enric Márquez Replace this with your values. I don't have a custom field with id 10160, so I used some dummy data at my end to reproduce you issue. 

Hi @Rebekah Myers I think I found the solution, this worked on my end. You need to set the value as a string. replace <name of id 10112> with the name of the option "customfield_10080" : [ { "value": "<name of id 10112>" } ]

Hi @Rebekah Myers Welcome to the community. Can you share your automation rule details and audit log? The error tells me that this is a required field on creating an issue, but the rule worked before as I understand before your request. Can you share the working rule details as well

Hi @Priyanka Gupta You can only to this within Xray in Jira. There are no API options. See the topic Test Set in the Xray documentation

Hi @Priyanka Gupta This part of the URL tell me you are on Atlassian Cloud "https://dremio.atlassian.net" Jira Server is self hosted and can't use the domain name atlasisan.net. So you are using Jira Software in the Cloud, the Xray API doesn't offer this action. See documentation on Xray Cloud.…

Hi @Aggeliki K That's a difference a reporter is just anyone who reported an issue, but if you specifically set a user of group, they require a license. There is no way circumventing this.

Hi @Sanjana Kumari On the marketplace listing they only mention it up to version 9.7. I would urge you to contact them directly, as they should be able to pride the answer as they are building and selling the product.

Hi @Durga Solse Will the following information provide you the correct context? How is the backup/restore handled in Atlassian Cloud? For Jira and Confluence Cloud, Atlassian utilises the snapshot feature of Amazon RDS (Amazon Relational Database Service) to create automated daily backups of each RDS instance. Amazon RDS…

Hi @Aggeliki K Does the single user been granted a JSM Agent license? Setting users relates to the same as setting a group of users, they require a license. Or If your JSM is combined with JSW and the user has a license for JSW the user should be able to see the issues with the set issue security option

Hi @Luc Evertzen Is the manual rule triggered from another project than the PT project and is that project a Team Managed project? If so in the edit action change the "Same Issue Type" to a specific Issue Type, as Team Managed projects are containers and no configuration is shared. But as @Jack Brickey mentioned, the audit…

Hi @Enric Márquez Welcome to the community. I would alter the rule to the following (replace the compare with your requirements) I have added the branch to find issues that are open as in your request and link to the trigger issue Most recently created issue doesn't have to the issue triggering this rule.

Hi @Sandesh TM On the Atlassian Developer platform you can find how to build apps and more. See: https://developer.atlassian.com/cloud/jira/platform/getting-started-with-forge/ 

Hi @안나연 What @Vishal is describing is the way I would use as well. As the "Share settings with an existing project" is only taking the schemes used, not automations and boards. As these functions are mostly always based on a single project and not globally used.

Hi @Sandeep Kumar In Jira Software you would need to create a custom field when using company managed projects. In Team Management project you can create also category field. Unfortunate they are all separate fields, a Custom field can be used in all company managed projects. But if a project is a Work Management or a Team…

Hi @George Mitsiou Welcome to the community. As Product Discovery projects act the same as team managed projects. The trigger occurs from one project to another, while the issue types are linked to a single project. You should adjust your rule, change within the create action "the same issue type" to the actual issue type…

Hi @Doug Reid I just saw the option I provided are for the new version to be installed in Server/DC. But the option you have represents the same.

Hi @[deleted] Welcome to the community The only fields that are able to show historic from in Jira vai JQL are: * Assignee * Fix Version * Priority * Reporter * Resolution * Status For the sub-task relation to parent there is no historic information in JQL There are apps on the marketplace that can export information to BI…

Hi @Doug Reid You can choose to use the Cloud Migration tool and just migrate the project or projects you select. For the users and groups, choose the option: Only users and groups related to the selected projects For the group membership preservation, choose the option: Migrate users and groups separately (the user won't…

Hi @Collista Lewingdon The default advanced roadmap team field is a fiedl created by Atlassian. This field is visible within the custom fields (all system created or app created fields and self created). The Team Field is a locked field and of the Type Team, this type of custom field can't be created. See: The screen you…

HI @Aggeliki K Are you able to share your config on the issue security scheme? And as @Vishal mentions, Customers are not affected by an Issue Security Scheme, the scheme only relates to JSM Agents.

Hi @Jana.Kyselova A customer can be a member of multiple organisation of a JSM project. You can just add the user to any organisation by email address