Matt Doar_tzgiej Community Champion

I just knew someone had to go meta on this one :)

Is this issue something filed for this question: https://jira.atlassian.com/browse/JRASERVER-66593

Nic, I forget, does the value of a scripted field usually depend on the cached data for the issue or what is in the Lucene index? I think it might be the former

My suspicion is that the many jobs could be due to the time on some server not being set as expected. Is ntp working? What timezones are involved?

type Jira, it corrects it, then use the Undo (Ctrl-Z for me) shortcut to undo the autocorrect

editMeta in the REST API should do that, or do you mean the Jira Java API?

It all depends what you want to use the data for. Some reports need structured data, so Jira is a good match. Other collaboration can work well with Confluence's less-structured data. Go with whatever gives you the results you want with the least friction for your teams.

That video says it is a workflow post function

Good point about default settings

Read all the docs on JSW, because that's part of how the exams were written. And really know all the reports. And play with a local instance of your own. Good luck!

Good summary. Yes, licenses should be updated before upgrading Atlassian apps in general. I guess your old license was due to expire on a date before the new software was released. It would be helpful to get a warning about this rather than a failed upgrade!

Perhaps the confusion is that Jira Service Desk is an app that can be installed in Jira Software? So the expected process would be to install Jira Software Server then add the Jira Service Desk application.

So I guess Server not Cloud since you can see the logs. If this is an evaluation, support is in this community

Me too!

Jira Server or Jira Cloud? And what messages are there in the log file?

"Upgrades do not appear to make any database changes." 6.x to 7.x did Ah yes, refreshing staging. That's true. I guess all you can do is automate the addition of your changes and removing them before a refresh. That's annoying

I'd write a custom condition using ScriptRunner. There be other apps that give you this kind of workflow condition

How is the security level for the issue set? You can use a custom post function on the Create transition to do things after that is known

Yup. Board, Configure, Columns and check for unmapped statuses

It;'s not surprising tto me hat custom DB changes could break the XML import. It's a one-off though, after you've migrated you won't have to do that again. Or perhaps at the next major upgrade. "We have no one in-house with Postgres experience" is more worrying for your long-term robustness of Jira. Not sure that Postgres…

The real question is why do you want that. You can sort by rank in JQL filter

A manual way is to look at all your permission schemes and notifications schemes for the groups they use. Then go through all project roles and do the same. Groups can also be used for sharing of filters and dashboards. Finally check all workflows for group usage in the XML. Very tedious! I would love to see a plugin that…

Sounds like Confluence has cached the user info from Jira. A restart of Confluence should fix it. Or perhaps just a full sync from the User Directory

That's funny! A product needs source code but it also needs a build system to create the product from the source code, and then documentation, and an ordering system and then all the other things software companies do. And if the person you trust ends up not being trustworthy, that's a risk with all relationships. If you…

Is that Jira Cloud?

But not for starter licenses. 

The rest of the log file should contain messages about why the issue were not imported. Note the message about only New items

A proper legal document such as an NDA is the first step I would take. And remember that just having the source code doesn't mean the other person has a working product.

Well, Chapters 3 and 4 of Practical Jira Administration (O'Reilly) are where I summarized this. Mail me at mdoar at my company name and I'll mail you the pdf of those two chapters

The basic idea is to define a collection of Jira schemes and use that collection for a set of related Jira projects, i.e. all the health care-related projects. Don't let other Jira admins change those schemes without discussing it with you. Add a description with strong words to those schemes