Matt Doar_tzgiej Community Champion

Good summary. Eventually all on-prem plugins (apps) will need to be Data Center approved (and priced) or become dead ends

update propertystring, propertyentry set propertystring.propertyvalue = 'https://jira-bet.mydomain.net' where propertystring.ID = propertyentry.ID and propertyentry.PROPERTY_KEY = 'jira.baseurl'; is how you do it in on-prem Jira. 

What if you have more than one subtask with different assignees?

"Should be 40-80 hours of work max" That depends on how large each instance is, how old the versions are, etc. It's probably ballpark though

This one worked like a charm for me, thank you! It's a great example of using an uncommon and. not well-documented Java API for Jira workflows, regex, and an XmlParser. Very useful

When issues are moved into DONE, is the system Resolution field being set?

If you have ScriptRunner then a Behaviour is the way. If not, then jira.issue.editable property in https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html for Server/Data Center

Ah, https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-issue-issueidorkey-attachments-post looks like it still doesn't let you set the create date 

Are the original users who uploaded the attachments, and the attachment creation dates, preserved?

Check the value of the dates in the database if you have access. Jira has problems if you enter dates far in the future, they get changed to negative values in the DB It's also possible that a CSV import was used to import invalid date values

Agile boards expect you to use Rank if you want to drag issues up and down.

I'm surprised that someone has done this operation 4999 times manually. But I'm more surprised that you would have more than 4999 screens in your Jira instance. Why do you have so many screens, is there a screen for every project for some reason?

Report it as a bug to Atlassian though

And what is the hyperlink?

Perhaps Atlassian Support will make such a change for you?

Or ask all your Jira admins

There is also an audit log on the Manage Apps page itself that might show more info

That's a long reindex! With Jira Data Center 8.5.4, 6.5 million issues, 1200 custom fields (mostly global contexts) we see a foreground reindex take under 4 hours. We do have jira-config.properties with jira.index.issue.threads=26

It's worth mentioning that if a JQL query is run for each event, the performance of Jira can suffer. We only use webhooks in transitions for this reason https://confluence.atlassian.com/jirakb/webhook-configuration-best-practices-952060713.html https://jira.atlassian.com/browse/JRASERVER-67421

Done. 

ScriptRunner has a job for this but it needs Jira 8.x to work

If you have the ScriptRunner plugin you should have access to the Java API for archiving a project. Or perhaps the Jira REST API can help with this https://docs.atlassian.com/software/jira/docs/api/REST/7.9.0/#api/2/project-archiveProject

We have our children decorate it. Results over the years have been ... mixed :) My main concern is that the stand should be sturdy enough so the cats don't topple it over!

Yup, leaving behind the commute. What a waste of time! Bringing forward an appreciation of the team I work in, and how it has worked in the last 9 months.

That's what I would expect too. Atlassian doesn't do patches. Fixes are provided as "patch" versions, so every patch is technically an upgrade. And upgrades are limited by their release dates and your last support date. But it would be good to get a confirmation from Atlassian on this

Mm, butter chicken

Try it without the role restriction as well?

That should be working, we use JSU validators for making fields required on transitions in many workflows. Might be worth checking that there is only one custom field with that name, and see if it works with a different custom field type? If it's still broken then I think it's time to file an issue with the JSU support…

Well deserved!

Find out the top 10 questions that people in the organization ask about the Atlassian products. Make sure you have written answers to those questions Use a tool such as Jira to track requests that are raised Get your support metrics in place early on We handle about 10 requests/day from about 5,000 active users, with a…