Matt Doar_tzgiej Community Champion

What kinds of configuration changes do you want the business users to make?

Perhaps https://marketplace.atlassian.com/apps/1210932/cute-for-jira?hosting=server&tab=pricing but not for Jira CLoud

I think that jira-rest-java-client was written for Jira Server not Jira Cloud? Not sure of good examples for the cloud

Perhaps with a ScriptRunner fragment. Not really the way the tool is intended to be used though.

https://confluence.atlassian.com/adminjiracloud/project-permissions-roles-and-issue-level-security-in-free-plans-976780344.html has more details about permission schemes in the free version: "Jira won't change any permissions, roles, or security schemes, as this could reveal project information that shouldn't be shared…

Sorting by that custom field would need to be done in the JQL that finds your issues. The script you show is processing each issue

Not that I know of. The REST API for retrieving issues and their fields does have a way to get the rendered value of the field. renderedIssue = jira.issue('TEST-17', expand='renderedFields') print renderedIssue.renderedFields.description

I think that there is a way to delete components using the REST API. https://docs.atlassian.com/software/jira/docs/api/REST/7.13.8/#api/2/component-delete

Botron or Adaptavist both have plugins that can help

I would be surprised if you can copy Xray info from dev into production without a valid Xray license in prod. Have you checked with the vendor, perhaps ask for an evaluation license. Once you purchase a license I would expect the vendor to want to help even more

Delete the field from production. Test the scripted field in your staging/test Jira instance Your script is vulnerable to admin error where closing or resolving an issue didn't set the Resolution field

I usually use project roles in permission schemes, but I do add the jira-administrators group to the Administrators permission. That way project admins cannot remove Jira admins from administering projects

That version is pretty old! I think the way to go is to set up Jira Cloud as you really want it, and tell people to start using it. Make the old Jira instance read-only for most projects. After six months consider shutting the old instance down. The main downside is that reports are messed up for a few months. This problem…

If you have ScriptRunner take a look at the steps https://scriptrunner.adaptavist.com/5.6.2/jira/jql-functions.html#_commented I think assignee might be a valid field to check for

Excellent summary! Because Jira Cloud and the other Jira Deployment types are built from different source code, they really are separate applications. New features can appear in one type and not the other. They have different REST APIs too. Jira Data Center nodes will have something after the version number and it might…

I don't see anywhere in the source that restricts the number of transitions shown to 15, but that's a number used elsewhere in the Jira UI, displaying components etc.

https://www.quipsupport.com/hc/en-us/articles/360002923051-How-do-I-integrate-Jira-and-Quip- and talk to your Jira admin

Contact your local Jira admin and ask to be added as a board admin

Do the security researchers have access to the source code of the vendors' apps? Or is this a closed system sort of thing.

Get some debug logging in there to show you what the JQL is being turned into for the Lucene query part. Use one of the Lucene index tools to analyze your index to check it is not changing.

You could even use issue security schemes to hide issues, or archive them if you have Data Center, or move them to a "retired" project. But there is no Jira trashbin. Just a small hole where your issue used to be.

That's a job for the vendor of Qmetry. https://marketplace.atlassian.com/apps/1215144/qmetry-test-management-for-jira?hosting=cloud&tab=support

Start with what reports people want to generate, and how those reports will actually make a different to the company. I would suggest to them that they can not use Sub-Component, but instead name the components better, something like this: Component A - Sub Component 1 Component A - Sub Component 2 Component B - Sub…

Probably need to clean the work directory. Also go to 64 bit Oracle JDK first, then move to OpenJDK. Only change one thing at a time

If you're in Cloud then yes. If you have DB access you can follow https://confluence.atlassian.com/jirakb/change-custom-field-types-in-jira-server-158357.html

Having duplicate names for custom fields in Jira, even for different field types, is usually considered to be bad practice. It confuses everyone eventually

Googling the error in the install log I found https://confluence.atlassian.com/jirakb/mysql-table-creation-fails-with-error-specified-key-was-too-long-235668644.html

I do have some other large models but the cats did a number of them and some repair is needed

This is what I'm going to make with my sons in July for our birthdays.

Nice keyboard. I've been using Goldtouch "gull wings" for about 20 years now. Saved my wrists Note the distracting chocolate box used as a monitor support