Comments
-
Hi @Ran Ziv I would suggest to bring this up at Atlassian Support. It might that some things are changed in the DB model and that old information was stored in that way, but not it's different.
-
Hi @stephen meyer This gadget is based on a 3rd party app called Rich Filter. This requires that you first create a Jira filter, then convert this to a Rich Filter. Then you could at the Rich Filter 2 dimension gadget and use the created Rich Filter. See Rich Filter documentation: Rich Filter Cloud
-
Hi @Divya Shree I do agree, but have a BUT. Labels are case sensitive, and can typos will create new labels and issues then could still fall outside the scope. example: Qa, qa, Dev would all be considered different labels and JQL on qa will only provide results based on qa and not include QA and/or Qa.
-
Hi @Ryan Lang This seems you are looking foor a ITAM or CMDB like solution. Atlassian offers Assets this is integrated within a cPremium subscription. Otherwise you could focus on 3rd party marketplace apps, see here And use search terms like ITAM, CMDB or Asset.
-
Hi @stephen meyer Can you show the current gadget used? Did you press the add gadgets and the load all gadget option?
-
HI @Rob Horan This would require you to use a 3rd party marketplace app. There are apps that can export date to Tableau, PowerBI, etc... See options here
-
Hio @Eric Kanagy If you use the parent field based on hierarchy, this is not considered a sub-task, but a parent child relation, this will not inherit the security level. Question, are your sub-tasks created in the same project or another project? If they are created in another project, there is no inheritance of the…
-
Hi @Eric Kanagy This document is based on on-prem installations, not the SaaS Cloud, but the same applies see: configure-issue-security-schemes
-
HI @Morgan Hall I do assume you have access via the API and get results, but you want to show only the results of the JQL and not a header row? I don't think this is possible, as Jira users a header row. Option could be to have another tab in your sheet and convert the information to your desire, use the JQL as source. But…
-
Hi @Jibitesh Chakraborty My 1st question is why? What do you want to accomplish by this? And as @Dick mentioned, Jira admins will always have this option.
-
Hi @Krisztina TEGLASI , So simply said, you dan't want devs to transition the issue to status "To Validate"? Then just set a condition on the workflow. You can use one of the following: * User Is In Project Role * Permission Condition In your case, I advice the 1st one.
-
Hi @Martin Vali In the create issue. If the assignee of the sub-task needs to be one of the users mentioned in the reviewers (multi-select field), set the Assignee to {{Reviewers}}. This is the name_of_the_advanced_branch. I would remove the reporter field from the fields to set.
-
Hi @Lucas Gagliano This can't be done. There is the autowatch global setting to be on or off. In a users profile a user can overwrite this for the user, this will be also for any created issue in any project global.
-
Hi @Alexandre Tirman Welcome. Are you project admin or Jira admin, also as this is a Jira Service Management project, have you been granted or can you grant yourself a JSM license? If you have a JSM license, do you have the role administrator and/or Service Desk Team on the project? If you are not Jira admin and the…
-
Hi @julian_fowler I don't know the app, but are the permission correct in both projects? Otherwise raise your issue at the 3rd party app support, as this is a 3rd party marketplace app. Or is there any stated in the documentation of the app in this?
-
Hi @Martin Vali You edit your previous comment I see, was just replying. Also set the assignee field in the create issue action. Set the assignee field to {{name_of_the_advanced_branch}}, I thought I saw {{Reviewer}} in your previous screenshot. Or see my screenshot and see the Reporter field.
-
Hi @Erik Stenersen That you could ask Atlassian? Or look and follow the Atlassian Cloud roadmap or see and search on Atlassian Jira (Feature and Bug requests)
-
Hi @Martin Vali Set the Parent field to "Trigger Issue" and if you want to use the summary from the parent issue. Use the smart value {{triggerIssue.summary}}
-
Hi @Chetan Shringi Welcome to the community I think this might be related to the workflow and the status the issue is in. It looks like properties have been set on the workflow status, the test is currently in. Certain roles, groups and or users could be excluded from editing. use-workflow-properties
-
Hi @David Blanco Welcome to the community. Based on the shown screenshot, we are talking on the Epic issue right, the issues are in the same project? Are the issue types using a different workflow, if they do, it might that the Epic workflow has statues set with properties that disallow editing for certain project roles,…
-
Hi @Erik Stenersen I you move your issues to the new project (my understanding in migration), all version release date is lost. See the following section in the documentation No, I don't see this possible as versions/releases are project specific and not transferable. Even continuing your work in a Company project, you are…
-
HI @Martin Vali Use the Advanced branching option. in the Advanced branching, set the variable to {{issue.customfield_<id>}} ,where <id> is the number of the custom field. how-to-find-any-custom-field-s-ids and set a name (to be used as variable if needed) Then use the Create Issue action and set it to create a sub-task,…
-
Hi @Gunjan Kumar Where would you like to see a table in the parent issue, or a you referring to the ootb linked Sub-taks information section in the parent issue?
-
HI @Jonathan Porta No you can't access or create custom ones, These options are native and the only available ones to be used within automation.
-
Hi @Nenad Neshov So the filter is there, is it working, so providing results and are the permissions on the filter still correct?
-
Hi @Christian Isaza Via the Jira UI and the projects option, you can order the projects by "Last Issue Update". Or look at the JIra API, based on Get projects paginated and use the orderby option and use the lastIssueUpdatedTime property or expand option and the insights property.
-
Hi @Jerry Norton Welcome. Not to sound "blonde", cloud you just type "releases", as you parent pages is called Releases?
-
HI @[deleted] You can look at this article, as there is no simple action/condition baed on mentioned user in a comment. automation-identify-users-mentioned-in-comment-and-add-them-to-custom-field What is actually stored in the comment when a user is mentioned is their account ID, not their name. The UI automatically…
-
HI @Ananda, Sampath Kumar These are related in a way. Opsgenie is an alerting tool that can sent messages to on call or standby users based on team rotations an send out triggers to escalation contacts etc.. It also just sets alerts not create issue JSM, this can be configured or manually triggered. This could also haapen…
-
Hi @Nenad Neshov As boards are based on filter, did you use an app like scriptrunner on the server side and use any related to the apps jql clauses in your filter? This would cause the filter not to be working on cLoud and maybe even not migrated. Can you check if the filter used in the board on the server side is migrated…