Nic Brough -Adaptavist- Expert

Behaviours does not yet work on Cloud, due to constraints on the platform, not Adaptavist coding! We're working with Atlassian to get it supported though. For now, you will have to look at alternatives - validators to check input and return people to the data screen with a warning about what they've done wrong, or seeing…

Yes, that's exactly what Scrum says on the most part. The bit that is not Scrum is "we expect stories to move across sprints". The whole point of a sprint is that you commit to completing a set of stories in it. You can't do that if a story is too big for a sprint. If you find you've got a large story, you should refine it…

The first paragraph is. The second paragraph is a better answer though - is there a reason you don't want to use the issue link field for what it is for?

Yes, that's the point. The roadmap only works off the issues you choose for the board. If you hide them from the board, the roadmap can't display them.

So nothing to do with JQL or searching. You could write a scripted field to drag it out of the history and comments, or you could write a listener to pick up all the change events (edit, assign, comment, transition, etc) and populate the field with the person who triggered the event.

Have a read through https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ to see if it can help.

I'd tend towards moving before - it'll be one less step to do while migrating.

Bug: When software does not behave as designed or intended. So this is not a bug, Jira is doing it as designed. Sprint estimates do not go on sub-tasks in Jira (If you do want to do it, you will need to implement a summing scheme, and unless you implement a scrum-aware one, you'll just make it a mess)

Welcome to the Atlassian Community! What exactly do you mean by "new environment" and what are you trying to migrate? Is this new environment a new Jira Server with a new database server behind it? (You're moving because your current servers are not powerful enough, or you want to move it onto a Cloud provider like AWS)…

>Sorry, but this is a wrong understanding of separation time and tasks with calculations of sums of it. Yes, but it's your understanding that is wrong, not Jira's. >This is a critical bug for JIRA, a bug of common sense. There is no bug in Jira here, it is behaving as designed and as intended. No, I'm afraid you are not…

Have you downloaded the source code? An installed server is a mix of template, display and config files, mixed in with classes and resources compiled from the source. It doesn't have the java code in it, only the compiled stuff.

Ok, Jira Software is not a standalone application. The installer is Jira Core + Software bundled together. Same as Jira Service Management - Core + JSM bundled. Atlassian don't do a bundle of all three together. The Jira Core installer will only upgrade Core, and you'd have to manually upgrade the other two after using it.…

Welcome to the Atlassian Community! Copy to what in AWS? Another Jira? A data store/warehouse/base? What reporting are you trying to do? (There are reporting tools for Jira that don't stress it) And what data are you trying to copy? If it's issue data, your best option for a copy is to use the REST API to extract what you…

Have a skim through the issues at https://jira.atlassian.com - a search for text ~ "notification scheme" AND summary ~ "issue type" AND resolution != duplicate Nets about 20, of which I think 5 are about notification schemes by issue type. They're all closed with "no one is interested in this" type comments - on the 5…

It's a doc next to the one you're reading - https://support.atlassian.com/jira-software-cloud/docs/create-a-new-project/ is in the side bar in the page you were reading.

No, they did not. To make Jira work with a proxy, you have to * Set up the proxy to talk to Jira and present itself to the intended network * Tell Jira it is behind a proxy * Change Jira's base url to match the proxy You don't have access to items 2 and 3 on Cloud.

Ok, you'll need to amend the field configuration that message is pointing to - you can click straight through to it from the link in the explanation message. Find reporter in the list and you'll find it has a "show" or "un hide" option to the right.

Start with a read through https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html The short answer though is * You can use the installer to do the upgrade in place - the best one for you to use would be Jira Software (that will upgrade Core and Software) * Then you can upgrade JSM from…

Please could you read Thiago's answer - it tells you what to do to prevent this being a security problem.

You would need to find or write a listener that can check what people put in the field and correct or clear it. However, why? Why are you doing this with a custom field? Why can't you simply ask your people to use issue links? They won't let people enter invalid issues and have a search function to help them find the right…

The easiest way to think of the backlog and sprint is that the sprint is simply the most highly ranked issues with a separator at the bottom of the segment. When you're in the backlog, you can drag things up into the sprint - this is just ranking them higher than the things you are not bringing into it. You can also drag…

Your query limits the data to just your epics so the roadmap has no stories to show! I would add Or (project = mkt and issuetype != epic)

Welcome to the Atlassian Community! Which Atlassian application is your "workday" system?

Welcome to the Atlassian Community! The problem here is that you cloned the story instead of putting it back into a not-done status. (By the way - " the team wanted credit for the work done in the current sprint" - that's not how Scrum works, you do not get partial credit for failing to complete a story you committed to.…

There might be two things you are talking about here. It might be the cancel button on the workflow pop-up where users are being asked for more information while they do the transition. I can't think of a good reason you would want to do that - all it does is make it harder to cancel the transition before it completes. And…

There's another conversation about these where Atlassian have asked us to send on spam from these dubious sites to https://www.atlassian.com/trust/report-abuse (forward the email with full headers, no more information needed)

What error message?

Welcome to the Atlassian Community! What is a "canny" account? And how are you "using it for Jira" - via Atlassian Access?

Given what the reporter and creator fields are for, I think you should be using the reporter as the target of the email, not the creator.

And sub-tasks?