DPKJ Community Champion

Can you create issue from UI, if yes make sure API is not returning cached response.

This isn't straight forward, if you are using Jira Server/DC you can use ScriptRunner for this. On cloud platform this seems not possible.

I used confluence for requirement, and linked Jira issue for coverage and implementation but traceability ended up as big problem. One more thing we missed was baseline of requirement. We ended up using RMsis a tool in Atlassian marketplace. This provide pretty awesome traceability with Jira issues and Test Cases.

@S_ Toyoit is time to get Atlassian Support guys in. I will be updating one of installation in day or two, and will confirm you if same issue occurs. (it may be version specific).

@S_ Toyohave you tried step "Decrypting the Password" to confirm that file generated have correct plaintext password in them.

You can do that using CRON jobs and Jira's rest API. * Just make a curl request to fetch all projects * Find those that match your criteria * Make a curl request to delete them one by one. This fetch all project in JSON format curl --request GET \ --url '/rest/api/3/project' \ --header 'Authorization: Bearer ' \ --header…

This is unusual. I have couple of suggestions, * You can check if your Jira Home settings points to correct directory, * what did you pasted in dbconfig.xml file?

You can do it as follows for AES key which falls in FIPS 140.2 - Typing json argument in terminal is not a good idea (as it won't be visible to you). You can open any text editor and prepare json in that, (replace <PASSWORD> with your original password) <span>{"plainTextPassword":"<PASSWORD>",…

You can do it as follows for AES key which falls in FIPS 140.2 - Typing json argument in terminal is not a good idea (as it won't be visible to you). You can open any text editor and prepare json in that, (replace <PASSWORD> with your original password) {<span>"plainTextPassword"</span>:<span>"<PASSWORD>"</span>,…

You can do it as follows for AES key which falls in FIPS 140.2 - Typing json argument in terminal is not a good idea (as it won't be visible to you). You can open any text editor and prepare json in that, (replace <PASSWORD> with your original password) {"plainTextPassword":"<PASSWORD>", "algorithm":"AES/CBC/PKCS5PADDING",…

What we did, - Created password related files at mentioned in STEP-1 - Moved all generated to filed to JIRA_USER home directory, and changed its mode to read only. $ mv javax.crypto.SealedObject* /home/<jira_user>/.config/jira/.<br>$ mv javax.crypto.spec.SecretKeySpec /home/<jira_user>/.config/jira/.<br>$ chmod -R 0444…

If you are using server/data-center version, 'robot.txt' is best solution to keep search engines away. You can find more details here - https://confluence.atlassian.com/display/DISC/Prevent+Search+Engine+Indexing+Using+Robots+Text+file

Sure, I read value using reflection api provided by Java.

Thanks.

My problem is I can't add direct dependency to Portfolio so that my plugin can run without it also. So it is important for me know what type of Object does it return.

I have looked into that answer. My issue is what does below code return? issue.getCustomFieldValue(parentLink); Can please tell me type of Object? Is it internal to Portfolio Plugin or is it standard Java issue type?

Thanks. I have searched for issues where "Parent Link IS NOT EMPTY" and there are some issues and I have run plugin code on those issues, and still I'm getting NULL as output for custom field value. But I will reverify it on new installation.

I was also thinking on same front. Thanks.

Was not able to reproduce this issue will try with other more browsers.

Will try to fix this ASAP.

I will try if I can include this feature, but I can't commit on timeline right now.

Thanks Renjith I got the basic idea there and it works.

I am using JIRA version 7.0.0 and this is the case in development mode using Atlassian SDK.

Has been fixed in version 1.5.6

Will try to fix this in next version. Thanks for reporting this.