Gregory Kneller Insider

Hi Vanessa, This looks like a great initiative - I’d be happy to take part. In my day-to-day work as a Jira/JSM architect, I already use a mix of AI approaches to analyze configurations and spot configuration debt (workflows, schemes, fields, permissions, etc.). This includes working with XML backups, AI-assisted analysis,…

may the users who has no permissions, see the field values in Issue Navigator?

If you’re lucky enough to have an Oracle database for your Data Center and just deleted some issues, you can try this to find them using SQL: SELECT * FROM JIRAISSUE AS OF TIMESTAMP (SYSTIMESTAMP - INTERVAL '15' MINUTE) MINUS SELECT * FROM JIRAISSUE; However, this works best for recent deletions. For deletions from…

Anarchists Cookbook for Jira, thank you, it is a great name! I am actually think about this writing 

Reporting from database, or even use sql results for scripts that do the changes using API, is not so risky as direct database manipulations

When a change is truly necessary and cannot be achieved through automation rules, APIs, or apps, I resort to XML manipulations in the cloud backup. However, this process is more complex than working with a database, will require downtime for users, and is challenging to test due to the lack of a test instance in the cloud.

I agree that testing is critical— and not just testing! I make backups of all tables I plan to change before making any modifications. But restarting Jira after database changes in my experience, is usually not required☠️ Here’s why: * Cleaning Jira’s Cache Often Resolves Most Issues Tools like ScriptRunner or SIL Engine…

Option 1. Use a Confluence Page for Each Project * * Set up a dedicated Confluence page for each project to document its current configuration. This page should include all relevant details, such as workflows, issue types, custom fields, permissions, and automation rules. Use "Project Page" feature in project configuration…

if your groups have very distinctive names, you may try to create database dump (dump.sql) and then perform shell script in unix: sed -e 's/"old-group-name"/"new-group-name"/g; s/"lower-case-old-group-name"/"lower-case-new-group-name"/g' dump.sql > newdump.sql Then you may try to attach the restored database to an empty…

Updating custom field values directly through Jira Query Language (JQL) is not feasible. While it's technically possible to modify the customfieldvalue table in the database—specifically the textvalue, stringvalue, datevalue, or numbervalue columns, depending on the field type — this approach carries significant risks. Not…

* Jira 8.8 and later: Audit logs are stored in the AO_C77861_AUDIT_ENTITY table. Confluence * Prior to Jira 8.8: Audit logs are stored in the audit_log table See https://confluence.atlassian.com/jirakb/accessing-jira-audit-information-through-the-database-695107926.html You may also use Audit Log…

In my cloud Jira at /secure/admin/CloudExport.jspa (System->Backup Manager): Backup for server is being discontinued starting June 30, 2025. It was previously planned for November 30, 2024. 

I believe this was indeed postponed to June 30, 2025 @Tim Eddelbüttel

the groovy code for data-center is in https://jira.atlassian.com/browse/JRASERVER-3132 

I have extensive experience of JIRA Cloud to Data Center and I can do this migration before November 30th, for those who can decide fast

* What were the reasons behind your decision to switch back? I assisted with a few similar migrations. The primary reasons were the acquisition of a smaller team using a cloud platform by a larger team operating in a data center * How did the transition back to on-prem work, and were there any lessons learned? There were…

Is it still open? In what country EU is the clients?

Again, I touch database continuously, because I perform migrations, clean-up and restructuring of JIRA. Some things may be done with scripting (Script Runner or Power Script), but other could be done only in database, in reasonable time. I had never "a lot of work from it", but it is my experience. Having database dump…

Nic, there is no REST API for many things. Sometimes database is the only way, of the fast shortcut. Database changes shall be applied with care and responsibility. If you are not sure, check in a test instance first, and create a copy of changed table. And you must know SQL. But nothing bad in select sql, RDBMS handles it…

SELECT u.lower_username, <span>u.user_key, </span>p.pkey, issuenum FROM jiraissue i, userassociation a, app_user u, project p<span> </span>where association_type='WatchIssue' and a.source_name=u.user_keyand i.id=sink_node_id<span> </span>and i.project=p.id<span> </span>

SELECT u.lower_username, concat(p.pkey,'-',issuenum)<span> </span>FROM jiraissue i, userassociation a, app_user u, project p<span> </span>where association_type='WatchIssue' and i.id=sink_node_id<span> </span><span> </span>and i.project=p.id<span> </span>and a.source_name=u.user_key

It is just an opinion. I use sql to read and change jira data since 2009. Fast, simple, and bypass security (I do not need it), no problems with performance

What country/city?