Comments
-
Hello @Rahul Joshi Could you please explain what exactly you wish to achieve and more details about the use-case
-
Hello @Piyush_Annadate If you want to update it "live on screen" i.e. update DoD based on the selection of component then the easiest way to it is to use the Behaviour module of the Script Runner plugin. https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html Sample here How to make a custom field default…
-
Hello @Klaus Foerschl I personally find using the native tild operator a bit unpredictable at times, thus If I have to write JQL like in your case to match string or part of it then I try using the Script Runner's JQL functions issueFieldExactMatch issueFieldMatch Can you modify your JQL to try any one of the above…
-
The addon has been archived by the plugin vendor https://www.adaptavist.com/doco/display/ASP/Advanced+Search+Plugin Possible Duplicate question - https://community.atlassian.com/t5/Confluence-questions/What-is-the-Advanced-Search-Macro/qaq-p/176783
-
Hello @Tracy Creer It currently doesn't seems possible to increase the result count from 5 to 15 without actually writing your own user macro or extending the existing macro by writing code.
-
And here's how you can setup the customer access https://confluence.atlassian.com/servicedeskcloud/set-up-customer-permissions-732528940.html If it's not a public facing Jira then it's better to select the option Anyone with an account on %your_Jira_Cloud_site%
-
Regarding your second question, from the docs Customers are automatically added to the Customers list if your service desk is open to users with Jira accounts or allows customers to create their own accounts.
-
Hello @Mark Anderson Both People and Customer are different entities. Customers are users who can report tickets on your service desk where as People are generally users who actually work on those tickets and are internal to your organization. Users who are in the "service-desk-team" role in the people's section are…
-
Hello @Hazel Hegde I am afraid there is no easy way to export a list of boards associated with an project please see some similar questions here https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-find-Boards-Filters-relating-to-a-specific-project/qaq-p/238180…
-
https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-create-a-custom-field-context-programmatically/qaq-p/517361
-
Hello @[deleted] You can't just add an single issueTYpe to an custom field configuration, you have to add an "context" which contains list of projects/issueTYpes mapped to that custom field. Please see some samples (using script runner - groovy)…
-
My second suggestion was for server (you can take cloud backup and restore on server)
-
Hello @Bachittar_Singh Jira stores data in structured format thus in order to search for anything you need to use JQL and provide relevant fields in query. Thus, which field in jira tickets was storing the URLs? As you need to search in that field instead of going through each field of the JIra. Another option you have is…
-
https://community.atlassian.com/t5/Marketplace-Apps-discussions/Suite-Utilities-for-JIRA-JSU-app-is-now-commercial/td-p/609117
-
Just to add to @Yogesh Mude answer, the details are here - https://community.atlassian.com/t5/Marketplace-Apps-discussions/Suite-Utilities-for-JIRA-JSU-app-is-now-commercial/td-p/609117
-
Hello @Sriram Nandakumar You can use the free version in the evaluation period but once evaluation period ends (generally 3 months) then you have to buy the plugin or it will be disabled automatically. It's a paid plugin thus you can't keep use it for free after a certain amount of time.…
-
Hello @Elena Oleksenko Did you try it, what was the outcome?
-
Hello @Sandy Greenberg Script runner gives you the function addedAfterSprintStart issueFunction in addedAfterSprintStart("Sample Scrum Board", "Sample Sprint 3") Since you want exact list at the start of sprint then you can write your JQL like Sprint = "Sample sprint 3" and issueFunction NOT in…
-
Could you try this code in script console and see if it returns expected result for the feature issue You can use the following code to to get issue object def issue = ComponentAccessor.issueManager.getIssueObject("<issue-key">) issueLinkManager.getOutwardLinks(issue.id)?.each {issueLink ->; def linkedIssue =…
-
Ok, then please go with the answer provided by @Mark Markov
-
Hello @zaharovvv_suek_ru You have to customize the screen scheme definition. Basically make sure that "Epic link" field is available on create and view screen and not present on edit screen. Please read the docs here as to how you can create screen scheme and map it with issueType…
-
Could you also may be try to execute the code with proper logging in the script console and use "IssueManager" to fetch the issueKey of an feature and see the output based on the above code if you get desired output or not.
-
Hello @Elena Oleksenko Is your Feature linked to an Epic via normal issue linking or via Epic link, because in that case an feature can be linked to not more than one epic.
-
Yes, upgrade to the JIra software version which you want and that should fix the problem. If you are having an commercial license then you can also take the opinion from the atlassian support https://support.atlassian.com/contact/ Though in the above link the answer is provided by atlassian support only.
-
Here's the link again https://community.atlassian.com/t5/Jira-Core-questions/Upgrading-when-you-have-both-JIRA-Software-and-JIRA-Core/qaq-p/727268
-
Hello @Jorge Mora Possible duplicate here - https://community.atlassian.com/t5/Jira-Core-questions/Upgrading-when-you-have-both-JIRA-Software-and-JIRA-Core/qaq-p/727268 Jira software is an application which provides agile features on top of Jira core. Thus, if you upgrade your Jira software then automatically jira core…
-
Hello @Fedor Sorokin You would then need to read up on the documentation about upgrading your jira instance because you need to be on the latest Jira server version and then migrate to cloud.
-
Hello @Raju Anumula You can take few different approaches for reducing the number of workflows, what I will do is follows - * Make a list of workflow schemes not mapped to any project * Make a list of workflows not mapped to any project * Try to find workflows which are similar in a way that they are using similar statuses…
-
Hello @Fedor Sorokin The migration guide is here https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html Please note that if you have tasks with let's say Assignee X and when you import the task into cloud and you want the task to have the same Assignee X then the Atlassian id(cloud)…
-
Hello @Ajinkya Group license is available for enterprises in the form of Atlassian stack. Please read this blog - https://www.atlassian.com/blog/devops/introducing-the-atlassian-stack-and-the-worlds-largest-devops-marketplace and license details here -https://www.atlassian.com/enterprise/stack