Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! You need to be very very careful when doing this, and take into account how Jira sees Agile processes (Scrum is not really an Agile process - I was doing Scrum before 17 people wrote the Agile manifesto, and had had my Scrum processes improved by one of them). Scrum is a very very very…

Welcome to the Atlassian Community! A column is a collection of issues in one or many mapped status from your workflow. If you don't have a status in your workflow, there's nothing a board can do. You need to talk to your project or Jira admins about adding a status to the workflow to represent "blocked"

Yep, Atlassian doesn't yet support building Behaviours in screens other than "create"

Welcome to the Atlassian Community! If your people are logging into the same URL, then one of your admins has changed the settings - possibly deleting or renaming a workspace. Could you give us a bit more detail than "workspace changed"? Is your old workspace available? Is it just the default? Have you checked all the…

Yes, your admins should not have created the new account. You can still delete it.

Your users should go into their old accounts, and change the email to the new one, not have your company set up a new account. If you change the email address to one that is under a managed domain, then you're converting the account from personal to managed (the individual loses the ability to change some of the…

Welcome to the Atlassian Community! Ending a sprint with incomplete items is not ideal, your teams should be talking about why they failed to complete the items they missed. "Invalidated" in this case is a good thing to use - you've obviously looked at the issue and made an active informed decision to not do it. In Scrum…

The managed accounts are the problem here - your site admins have been creating new accounts instead of changing the existing ones. You'll need to get them to stop that, and have them edit the existing accounts.

A post-function is a chunk of code that is run once a transition has been validated and confirmed (a transition is a change of status). They are implemented in workflows in the project. You can find these in the project settings (For company-managed, in the workflow scheme, for team-managed, they're under each issue type)

Welcome to the Atlassian Community! First, my usual advice - reporting off a Jira database is the worst possible way you can report on Jira. It's slow, ugly ("show me issue X" takes 12 joins before you triple that with adding "in human language" to the question) and you will probably not understand the answers it gives…

Story points is not going to help you generate accurate reporting - you need your people to put good estimates in, it doesn't matter what format the estimate is in, you just need to train your people to do it right. Putting it into one field and then translating it to another one is utterly pointless, it's actually likely…

There is no way to do this. To grant permissions to someone, you have to be able identify them as someone, and that means making them a Jira user. There is one exception - you can grant the group "anonymous" permissions. People won't need to be identified to use that, so the world would all be "non Jira users" Be warned…

You won't find any alternatives - you can't stop people having more than one account. The best you can do is have your people administrators do checks on the accounts before you add them into your systems.

Why don't you just use the estimate fields directly? Story points are not useful as a proxy for time, they are intended to be a way to size stories against each other so you can work out what the team can get done in a sprint. If you're using them as hours, you're just over-complexifying your setup. Get your people to put…

This is incorrect. Admin rights give you admin rights, not "can see/do anything"

There's no shortcuts to this, unless you are willing to script something that can amend your permission schemes over the REST API.

Welcome to the Atlassian Community! For a field to be presented to a user in a Company-managed project (all server/dc projects are), then it must * Be on the screen, as you've shown us a screenshot of * Not be hidden in the field configuration for the issue type and project * Have context for the issue type and project So…

Again, you need to define what you mean by planned and actual progress. When you know that, you can run searches over REST to return the data you are looking for.

Welcome to the Atlassian Community! The page is probably restricted to who can edit it. You'll need one of the people who can edit it to add you to the restriction (talk to your space admins first, to identify the people who can edit it so you can ask them to add you)

This won't work. Customer accounts can only see requests in the portal, they won't see the issues you migrate from Software to Service-Management, because the issues don't have requests.

Welcome to the Atlassian Community! There are a couple of simple ways to do this. You can label pages with categories (this feeds into the search), or you could organise your pages into a hierarchy, with parent pages representing categories.

The easiest thing to do is right-click on the image you want to download and use the browser's image tools to save it. You can also do this in space administration (the image won't be scaled in there) - I can't remember which tab it is for DC, but look in the overview and sidebar tabs first.

Welcome to the Atlassian Community! Your "requirement" is wrong. You don't want to use the database to get this data, it is the worst possible way you can report on Jira issues. You would need to write hideously complex SQL that has the potential to You have not defined what you mean by planned and actual progress either,…

Welcome to the Atlassian Community! What do you mean by "download the key"? The key is made available in your account and you just need to copy and paste it, no download needed.

Welcome to the Atlassian Community! In Scrum, there is no partial completion, you either delivered or you did not. If a story is not completed, then it rolls over into the next sprint (assuming the team agrees it is still high on the to-do list) The "credit" is irrelevant, you only get credited when you complete an item.

I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software. The popup means what it says - you have given your system a licence that is not right for the app or application you are licencing. You will need to check your application…

Welcome to the Atlassian Community! Um, install it and run it on both machines. I'm not sure what you are really asking about here - Sourcetree is software that you can run on a lot of devices.

I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software. The workflow is not relevant to what a board selects for display. Your filter looks absolutely fine to me, I suspect your closed/resolved clauses are simply excluding your…

It sounds like your users are not changing their email addresses, but creating new accounts with new email addresses. You need to ask them to change the email addresses on their Atlassian accounts (or do it for them if you are using managed accounts, or your company directory) Your admins also should stop using "suggest…

"View all issues" is already proving to be the wrong name - people are asking questions about why it's changed and how it is limited when it says "all" here and on Slack. I'm with @Rick Westbrock - "search issues" is more clear.