Alexey Matveev Expert

Then you can create a new Jira Cloud instance. Take a backup and import this backup to your current Jira.

Hi @Sally Lopez _CSB014_ ! Yes, you can go Issues-> Search issues and then type the following JQL query: issuetype = epic and "Epic Status" = Done or the query typed by @Craig Nodwell . It depends how you mark your Epics as done

Hello Doug! A Connect app can be developed in any language. But I suppose that you use React for UI. If so, it makes sense to use atlaskit and the Table Tree element: https://atlassian.design/components/table-tree/

Hello Olexandr! Please, have a look at this KB article: https://confluence.atlassian.com/cloudkb/reset-and-delete-all-data-from-your-cloud-site-691012037.html

Hello! Thank you! Actually I can remember my first answer well. It was accepted by @Andy Heinzer . I always wanted to tell him thanks and I was able to do it during Atlassian Summit in US in 2019 ) I am very grateful to you that you accepted me to Community and It s been always my pleasure to be part of our great team!…

Hello @Greg Chapman , I believe that you should use a JQL like this: key in silJQLExpression('startOfDay(created) < startOfDay(#{Start Date} - "5d")', 'project = YourProjectKey') It would be nice if you had mentioned that you use Power Scripts in your question. In this case I would find your ticket faster. Thank you! 

@Sami Ahmed Shaik , Please create a support ticket with Cprime: https://jira.cprime.io/servicedesk/customer/portal/2

@Dan Koester You can try the free version, though there are could be problems with your instance while upgrading or installing the app. You instance can freeze for a long period of time. We have not found other problems so far. But you may have other problems as well.

Hello @Anuradha Wishmantha , What metrics would you like to gather? Available metrics would be this ones: * ssue:comment_created * issue:created * issue:updated * project:updated * pullrequest:approved * pullrequest:comment_created * pullrequest:comment_deleted * pullrequest:created * pullrequest:fulfilled *…

@Sami Ahmed Shaik Could you paste the error? I believe the message is not complete.

@Mesut Can , I can not help you with it. I do not have a windows PC. Sorry.

@Sami Ahmed Shaik You code looks correct to me. You need to debug it. Add a logPrint("ERROR", "your message") ; to your code and have a look what messages you have. You should make sure that your code has been executed. Also look for errors in the atlassian-jira.log file

Hello! You can use Live Fields. Suppose you have customfield_10101, customfield_10102, customfield_10103, customfield_10104, customfield_10105. First create a file setValueForCustomField10105.sil: number val = (argv["customfield_10101"] + argv["customfield_10102"] + argv["customfield_10103"]) /argv["customfield_10104"];…

@Sami Ahmed Shaik , 1. remove the Checkbox field from the Edit screen (changes in the Edit screen can be caught only be a listener) 2. Create a screen with the Checkbox field in it. 3. Create a transition with this screen. 4. Add a post function to this transition as the last but one (before triggering event) with the code…

Hello @Sami Ahmed Shaik , You can create a listener for the Update Issue event with a code like this: JFieldChange [] changes = lastIssueChanges(key); for(number i = 0; i < size(changes); i++) { if (changes[i].field == "customfield_XXXXXX") { addComment(key, currentUser(), replace(key.customfield_XXXXXX, "|", "\n"));…

@Ashok Kumar Srinivas , The metrics you are mentioning are mbeans in the JVM. Prometheus for Confluence app can pull those mbeans but Prometheus for Jira can not do it (it is not implemented in Prometheus for Jira app). That is why you can create a feature request for Prometheus for Jira app or use JMX exporter. Those…

Hello @Ashok Kumar Srinivas ! Those metrics are not available from the Prometheus for Jira app. If you want those metrics to be available, kindly create a feature request here: https://jira.cprime.io/servicedesk/customer/portal/2 Or you can use Prometheus JMX exporter to get these metrics to Prometheus.

or use Jira Rest Api to create an issue.

I believe that if you want to make it work as you expect it to work, you should create a ticket with cprime support but I think it will not be a fast fix. Or you can add a custom field called SIL created. If this field is set to 0 by default, then your validator will check the issue, if to 1 then your validator will not…

Hello @Błażej O_ , If a field is required then an issue can not be created via UI or REST API if the required field is not set, but in SIL you can still create such an issue. That is why your code would be like this: KPOption nopt; nopt.label = "my_label"; nopt.value = "my_value"; string[] CFmappings = {"assignee", "me"};…

@Sami Ahmed Shaik , You are most welcome!

You should do it this way. Checklist (Checkbox CF) and Action Item List(Checkbox CF) should have the same options. then you create a live field with code like this: string [] val = customfield_10400; lfAllowSelectOptions("customfield_10402", val);

It is not how Jira works. Please, let me know what you are trying to achieve. I will help you to solve it the Jira way.

The correct way would be: customfield_10402 = customfield_10400; This line will copy selected values in customfield_10400 into cusotmfield_10402 For example, You have customfield_1400 with options Yes and No and Yes is selected. Also you have customfield_10401 with options Yes, No, Maybe. After the line above has been…

Hello @Sami Ahmed Shaik , If you use Jira Cloud, then you can use the "Copy Value from Other Field" post function mentioned by @Andrew Morin . If you use Jira Server than this post function is not available. You should use the SIL post function with a code like this: #{Checkbox CF2} = #{Checkbox CF1}

Hello @James Muir , Try to write like this: customfield_10077 =getUserByFullName("Jane Doe");

If you run it in console, you need to provide the issue key in the Run Configuration dialog screen:

Hello @Meital , If this bug is still valid for you. Please, register a ticket in Cprime support system: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview I also have the same problem with the URL field.

Hello @Danny Davidson , I would create a workflow, which would include all necessary statuses for Type A or Type B and then use workflow conditions to show required statuses. For example, Let's say you have a status named Open. Then for Epic Type A you need to go from Open to Under Review and for Epic Type B you need to go…

Hello @Daniel Völker , The only way to find out if an issue was cloned, if you clone issues with a link to the source issue. Then you can have a look if an issue has the "cloned by" link and if it has, then this issue was cloned.