Matt Doar_tzgiej Community Champion

I think I'd keep one project with multiple versions

Another valid reason for a new project is when access to a project needs to change. Different permission schemes, project roles, issue security schemes. And a reason that is not documented, so not in the exams, is that some admin actions start to time out when you have a large Jira instance and more than about 50K issues…

Very true.

https://confluence.atlassian.com/jirakb/how-to-unlock-a-locked-jira-software-field-779158866.html I've also done it with a ScriptRunner script before Careful not to change the name or custom field context or you may break a plugin. Test in staging first.

And now they cost too much to be an easy buy on Ebay. Ah well.

I have one of those consoles in my garage I think, from a junque sale over twenty years ago. One of my best presents was a Vertibird. This little helicopter on a rod toy was so much fun I bought one to play with my own children some years ago. The cat loved it too.

Good article! And I know what you mean about the numbers. They are there to make an impact I imagine. They certainly surprise me as well

Not without careful testing and checking with Support. But we run without the Jira plugin that pops up things for new users in production. 

My money is on Confluence Activity Stream Plugin

How about finding which add-on module provides the Activity Stream and disabling that module? In staging of course. May need some source code searching to find the exact add-on and module name

Sometimes an issue in another project is using the same sprint. That happens if you moved the issue. Check for that with sprint = nnnn and project != ABC

That's useful, thanks

If the URL for each attachment is available publicly with no authentication it should work. Otherwise the REST API will work, but all the author values are set to the user who logged in

Arturo Fuente Opus X, after successful Jira upgrades. 

All boards have a JQL filter defined. The way that JQL is written can affect which statuses are shown on a board

If you are not seeing an expected Status in the unmapped Statuses column, it may be due to your board filter using OR clauses. Please can you add it here

That is the general idea. Make sure you are comfortable with the editor you choose to use. Use shutdown.sh rather than stop-jira.sh to avoid a kill-9 corrupting the Lucene index files

Yes, though you could also use emacs

Start with https://confluence.atlassian.com/adminjiraserver073/increasing-jira-application-memory-861253796.html

I use Data Center and Script Runner, so I just log in as the owner of the filter. This may be the same problem in Cloud with no workaround. Contact Atlassian support?

Yes, it's not a common approach but we like it because it gives us a sense of what our customers are experiencing Jira. We use an internal Jira user as the service account, with the internal user directory first in the list of directories. So the absolute values for that metric are probably a little better than our AD…

We use a custom app for combining the metrics on different pages

Then we have a dashboard that combines all the metrics, and alerts that are triggered by levels and duration. The alerts are processed by a custom service that decides who to contact depending on on-call schedules and personal preferences. The alert info also contains links to Wiki pages about handling the problem.

We have a number of different ways we monitor Jira. 1. We have a script that creates, updates and deletes an issue every minute on each node of our 4 node cluster. The time for each of those tells us what users are experiencing 2. We use the Health Check REST endpoint to monitor all of those health checks every minute…

My suggestion is to check with your Legal team about the company data retention policy. You may find they would prefer that data not be deleted. Archiving should be fine but it only Data Center right now I believe.

Earlier discussion is at https://community.atlassian.com/t5/Agility-Beta-questions/Are-you-oversimplifying-Jira/qaq-p/742877

Based on Atlassian consulting for over 150 companies over a dozen years, two O'Reilly Jira books, writing multiple commercial plugins ,and running a 4 million issue Jira Data Center instance. But I still recommend Jira for most use cases.

Jira Cloud and Server are not the same product, and are diverging more with next-gen. That's fine and expected. Large Jira instances are all Server or Data Center because Cloud is not intended for that scale Jira PMs hear the complaint that Jira is hard to configure and needs a Jira administrator for too many things. That…

Use a Workflow validator for transitions where you want to make sure that work is logged. Then don't put a validator in the Backlog to In Progress transition

I think you could use the App Link set up between your Jira and your Confluence to modify Confluence pages