Nic Brough -Adaptavist- Expert

Go to "global permissions" in Confluence, and add the group that allows access to Jira into the permission for using confluence as well.

For an issue to appear on a board , it needs to be selected and shown by the board. If you remove status from the board (by not mapping them into a column), then you are telling Jira that the issues should not be selected for view, which means they should not be in the backlog. You do not need a to-do column to be there…

How are you "assigning a story to a feature"?

Inactive workflows do not need to be published, you edit them and save the changes.

Update on what issue? Meta data is usually added to Confluence with labels and page properties, have you tried those?

You can get your existing key from https://my.atlassian.com

>The installation will start and after it finishes I login to localhost:8080 and I find out that I have Jira service disk only without Jira core This is incorrect. Jira Service Desk is an application that runs on top of Jira Core. It can't work without Core. If you're seeing Jira Service Desk working, you have Core working…

This error means what it says - the field you are trying to set is not on the edit screen for the issue. However, this might also be caused by the user you are using not having access to edit (because they are not logged in, or don't have edit permission)

There's no way to amend that list without code

I think it's in createissue-start.jsp but bear in mind that is only one place you can create issues, there are a lot of others.

You need to do what the error message tells you. By "fix" it means make someone else the primary billing contact and technical contact on all the products you have.

No, Confluence is not a file store, it has a simple flat "files on this page" structure. If you need "folders", you do it by nesting the pages that the attachments are added to.

Sub tasks are in the sprint that their parent is in. Are you saying that you have stories in another sprint that are showing as being in the current one?

If you want to remove the linked applications completely, go to Admin -> Application links and remove the links. This will, of course, disable all the functions you get from the links as well as removing the menu item

Possibly a bug, but you'd need to ask SAP if they have it logged as such, because it's not a bug in Jira.

Could you explain what you mean by "primary list of filters"?

So have you ever worked in a place that uses software that allows multiple assignees? If you have, you will have seen a lot of "I thought someone else was working on it". Which is, of course, a complete failure.

There's no "push back" above, there's a load of help to guide them on how they can get their systems to work better for them and an explanation of why "archiving" has a specific meaning that is not what they're actually trying to do. >Back to archiving. Each test, test set, test plan, task, sprint, etc needs to have a…

As above. Go to your account, then settings, and click delete. If that does not give you an "account deleted" message, you will need to deal with the error message it gives you. If you get an unexpected response and want our help with it, you need to tell us what the error(s) are.

Yay! Please, everyone strive for this. There are so many superb answers in the community, I have (almost) stopped asking questions. But things change, and, to be completely selfish, I don't want to fall behind the changes, so I rely on other people's answers a lot. And although I know some answers get no useful response or…

Ah, ok, that happens when the server cannot talk to itself properly over REST, or the remote server asking for the gadgets can't. I'm not sure what server you are talking about, but if I take a sample set up of "Server 1 is running Jira and Server 2 is running Confluence" and "Server 2 is trying to import gadgets from…

I can't say if other people in your area are active in the community, and it would be rude to just name people without checking with them first. But I can tell you that I am aware of organisations using Atlassian stuff in Bristol, Bath, Cardiff, Swindon, Cheltenham, Gloucester, and several others (which if I named, would…

Ok, I'm afraid the new issue view does not have the roll-up function that the old one does. You can still see it in searches in the issue navigator if you add the Σ estimate fields to the columns, as well as the old view.

No undying love I'm afraid, but Jira does have a REST API you can talk to (presupposing NIRG has extension points that allow you to code for it to talk to Jira), and ways to write code that would live in Jira and read/write NIRG (again, assuming NIRG has a remote API, or at least an interface that could be called…

You will need to talk to your administrators about logging into your system. I'm afraid I can't tell you who they are, I'm just an end-user of Atlassian stuff, like most people here. I would ask the people you work with and maybe the person who invited you or initially set you up.

Check the functions on the workflow transition that is not working, and if they look like they should be working, contact Atlassian Support 

I know, it annoys me too, it's a silly flaw. There's a longer thread somewhere else on the same subject, with an explanation from an Atlassian which is a bit sketchy about how the mistake was made, but a lot of detail about why it's not going to be fixed.

Jira presents fields to us humans on "screens", which are nothing more than a list of fields in a certain order. Each project/issue-type can be set to use different screens, although most of us tend to keep it simple and share screens so that things tend to look and behave the same. There are four ways a screen comes into…

There is no way to do what you say in the title. The workflow is determined by the choice of issue type and project, and what the workflow scheme says it should be for that choice. But you can route through a workflow with custom field data. I use "contrary pairs" of "conditions" to do this. In your example, I would *…

The word "awesome" was used to say "thank you for suggesting a workaround", by one person, not "everyone".