Tuncay Senturk _Snapbytes_ Community Champion

Hi @Vinod Rathod (Contractor) Welcome to the Atlassian Community! You need to be more specific if you want help from the community. 400 error codes are the client-side errors such as URL, HTTP method and payload mistakes. Could you please tell us more about the REST request: which URL are you calling? Method, and are you…

Awesome! Thanks @Nikki Zavadska _Appfire_

Hi @RKamboj Welcome to the Atlassian Community! Checking the status page (https://zephyr-scale.statuspage.io/) for Zephyr Scale, I could not see any problem recently. So, I think it is best to raise a ticket to the vendor if you are still facing the same problem. Here is the link to their support portal:…

Both are OK. But please bear in mind that if you use single quote, you can't use single wuote within the jql. It's same for the double quotes. But if you use three double quotes, you are free to use any :)

Hi @Aisha M It must have been the quotes. Put your jql within three quotes, like this parseQuery(""" query """ )

Oh, I see, my bad! If you change this line if (counter++ > 500) to this if (++counter > 500) it will not pick +1 :) 

Pleasure!

Hi @Sindhu Pullapantula Welcome to the Atlassian Community! There is an open ticket on Atlassian for this purpose: JRACLOUD-21372 Don't forget to vote/watch the issue!

Yeah, I know, I'm sorry. I just shared because those were the ones which were shared already in the issue.

Hmm, I see. I don't know whether they meet your expectation but these are the apps that are shared in that issue already. I could not see they change the look&feel in the issue navigator though * Links Hierarchy Structure * Structure for JIRA.

Hi @Nal Premik Welcome to the Atlassian Community! There used to be a ticket regarding this request. JRASERVER-32093 Unfortunately, it was closed with Won't Do. You can't do that out-of-the-box. You have to search apps to do that.

Hi @Anna Vincent It seems there is already an issue which has been in Gathering Impact status: JRASERVER-66329

I'm glad it worked. @Aisha M you can test it with 3 issues, changing 500 to 3 and testing with a JQL which will return 5 issues. You know where to change in code to test, after a successful result you can change back to 500.

Those are info level logs, don't worry about them. I'm glad it worked :) 

These logs are not the ones I needed actually. Are you sure the issue was archived? So, no need to add any log. So, please make sure and change the code accordingly, I mean please do not forget to change the JQL to whatever you want to get the appropriate list of issues which will be archived. if all is sorted, then happy…

Aaah sorry! please use log instead of logger :) 

Now the fun begins... What I'd suggest is to add some logs so that we can see whether the API calls are done successfully. def validationResult = archivedIssueService.validateArchiveIssue(user, issue.getKey(), NOTIFY_USERS); logger.error ("validationResult: $validationResult") if (validationResult.isValid()) { logger.error…

Ok, can you simply put the below line at the end of the script? return null

Hi @Aisha M Are there any other log messages? This error message did not ring the bell.

Oh! sorry! Thanks for the screenshot. Please use issue.getKey() instead of it.getKey() By the way, I recommend testing with a specific issue, providing JQL like key = ABC-2334

Ok, so the first one should definitely work. As you can see in the screenshot you shared there is a method validateArchiveIssue(ApplicationUser, String, boolean) So, please make sure you use : def validationResult = archivedIssueService.validateArchiveIssue(user, it.getKey(), false);

This will be tricky! After typing below which code assisted methods do you see? You can get the list by clicking Ctrl + Space, I believe. archivedIssueService.

But, please keep in mind that if you upgrade your Jira, you will need to change that again :( 

Hi @Aisha M It is because of your DC version. In previous versions of DC, there is no third parameter (NOTIFY_USERS) which is the decision to notify users about the archiving. Please change that part as below def validationResult = archivedIssueService.validateArchiveIssue(user, it.getKey());

Sorry, I don't have DC instance either, that's why I can't try the code. I changed the related part as below, pls try that one. Btw, I only tried to help with the archiving issue part. Not the sending email job. import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.component.ComponentAccessor…

Sorry, it wasn't clear. The below code might help you even more. It has the script to fetch those issues, control exceeding 500, and the code archiving the issue. import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.component.ComponentAccessor import…

Hi @Aisha M Thanks for summoning me :) Did you try to filter those issues and archive each of them using Groovy script? I can't help you with the entire code but this might be a good starting point. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.archiving.ArchivedIssueService…

Hi @이의석 If you recalculate/regenerate SLA data, do you see accurate results for those issues? Probably, we will need details. Could you please raise a ticket here the support team will respond shortly.

Hi @[deleted] Welcome to the Atlassian Community! Please check this post, it might help.

Really interesting workaround! Thanks for sharing. I wouldn't do that but it would be a good option for those who can't live without freezing the summary.