Bulk updating date field based on comment text and date

[Chris Ripley-Duggan]

Hi all,

We have a custom "Publication Date" field that I'm attempting to bulk populate. I'm looking to set that field to the date that a comment was added which features a particular URL.

I've already created a project-based automation to achieve this going forward, but now wondering if I can bulk update the ~300 existing tasks...I have a horrible feeling I cannot, but thought I would ask! Thank you!

[Peter DeWitt]

@sahoo subrat, a few thoughts:

1. make sure you're permissions for the add-ons folder are correct.

2. make sure your permissions for the add-on .jar are correct.

3. if permissions aren't the issue, try shutting Jira down, and deleting add-on .jar files for the add-ons giving you problems.  You could then either add the new updated .jar files directly to add-on folder or restart Jira and use the add-on interface to upload the new .jar.  

[sahoo subrat]

@Peter DeWitt yeah understood, but i did try these options already. And note that we are running these on VM's, & i took a clone from the production. So the system, permissions etc everything is same as on PROD. I am confused what might be causing the problem. 

Was expecting that it might be a firewall issue/cert issue/java but everything looks good. Now i am stuck and don't know what to be done

[Peter DeWitt]

That is pretty strange.  Have you tried manually deleting the existing version and then trying to upload the add-ons as normal?

[sahoo subrat]

@Peter DeWitt Yes i did try that option too, still the same

[Victor Mutambuki]

Sahoo,

You must be a JIRA system admin to do so. If you're only a jira admin, you will only be able to update add-ons.

https://confluence.atlassian.com/adminjiraserver073/managing-global-permissions-861253290.html

Victor

[sahoo subrat]

@Victor Mutambuki I am actually an administrator for both jira and confluence. I clearly mentioned that i am able to update plugins which are from atlassian, but the problem is with third party plugins and the problem is present only on my test environment