Nic Brough -Adaptavist- Expert

This is because Behaviours have to be done last when doing the page rendering. Jira pages can be very heavy on the javascript and it can take a while for it to all load and execute, and as the Behaviour is last, you're seeing it execute at the end.

There is no image attached. Could you give us the text of the error message?

It appears automatically on transition screens (if the user has "comment" permission). It cannot be added to the create screen. Create expects you to put all the data into the fields, not be the first to comment on it. If you feel like a comment is useful on a new issue, it should almost certainly be in the body of the…

Follow the upgrade doc I gave a link to. I'm sorry, I can't tell you much more than that. You have not told us where you are stuck (or where you have, we've told you how to proceed), so all we can really say is "do the upgrade as per docs"

You'll need to move back to a supported postgres version. Ideally, directly, by taking a database export of the v12 one and restoring it into a v9. But you might want to try the xml export if that won't work. (Problem with the xml export is that it reads the entire database, so if there are problems with v12, you may lose…

Ahh, excellent, that's where I was headed when I opened the question again to respond!

Please see the conversation above about how to work around it, and about why it's not been fixed.

The workaround works fine - make a copy, add the transition in there, migrate over to it.

What base urls do you use for them? I don't need to know, just whether they're the same or not. For example, if you get to JSW on jsw.atlassian.net/xxxxx and JSM on jsm.atlassian.net/xxxxxx, they are separate instances. If they're both on yourdomain.atlassian.net, then they're on the same system, and the "integration" is…

This suggests something is running which tries to set an issue status and either fails or does not index after doing it. Do you have any scripts or automations that might be changing the status of issues?

Are they both the same Jira, or two separate instances?

Dashboards are not project artefacts, they're global landing pages which could refer to many projects. Are you talking about something other than a Jira dashboard?

This is a Java problem, not a Jira or even Tomcat (the application server that runs Jira) one. The java virtual machine caches DNS results by default. So when your Jira is trying to connect to mail.domain.com, it is not looking the name up on every connection, it's been given the cached result by Java. Your round-robin dns…

Upgrating to JSM won't help you here. The Cloud migration assistant doesn't do most of JSD or JSM into the Cloud at all. The list of what it does and doesn't do is at https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/ and "Jira Service Management projects (formerly Jira…

Are the people who can upload larger files Confluence administrators? If they are not, then you'll need to raise this with Atlassian as something is broken, it should be limiting uploads to 10Mb (for what it's worth, the limit seems to take a couple of minutes to apply on the Cloud install I've just tested with, but it did…

Yes it can do that if you tweak it a bit to aim at the groups. It is a Scriptrunner script, so Aiden built it to be run in the SR console

Apps need to be licenced for the highest tier of Jira application you have. So no, you need to licence Zephyr for 100 people, as that's how many could use it. If, for example, you have licences for 3 Service Desk Agents, 50 Software users and 100 Core users, all apps you add to the system need to be licenced for 100 users,…

No, you're not lying. There's no question that you're lying, or doing anything wrong - you are not. You just need to think through your use of Atlassian tools on the various databases you are might use

No, nothing, collaboration software is for sharing, not hiding things from others you want to to work with.

Ok, so I don't think it's the usual problem. I think you will need to talk to your people to educate them that it takes a few seconds for their browsers to do all the work.

Solved in the community means "we had an understandable answer", not "it is fixed". Views are irrelevant. Votes count,and I suspect that "only 20" puts it low down on the list of Atlassian priorities.

That was exactly my point, it's not about the downloads. The attachment size setting is to stop oversized uploads. I do not understand your problem here. Could you explain what you expect and what you get?

Force AWS to go back to a supported platform. That's facecious - AWS did not force anything, they suggested. You should be able to say "no" and stick with a supported database for now. And aske to move back, without AWS questioning it.

I am sorry, but what you have said makes no sense. There is no such thing as "status ranking" and we need you to explain what you think this is. I would like to look at your example, but only the bits that are unclear: You say "If status is created to workflow without any order " * What is "status created to workflow"? *…

What do your logs say the upgrade errors are?

You really need to find out what is causing the increments. Have you got any mail set up for this?

mmm, I'd worry about that too. I can't access the video either, but I'd like to, as I'd want to see how it handles the cases where issue configs are different (especially workflow)

This needs to go to Xray rather than Atlassian, the indexing on Cloud is automatic.

The maximum attachment size only stops you uploading large files. It has no effect on the download of existing files

It depends on if this is a classic project or a next-gen one, but you can tell that from the bottom left where there will be a "configure project" link If you have a next-gen project, then your agent can go into configure, find the request and issue type, go to the issue type, find the field and add options to it If it is…