Nic Brough -Adaptavist- Expert

Atlassian software is a huge field and "how do I get around" is too vague a question for most of us can begin to answer. We're here to talk about Atlassian stuff, not tell you how to use websites. Best I can do is tell you to look at the purpose behind each thing and use it as intended. Jira is an issue tracker, give it a…

Ok, but do you mean when they are actively in the screen and entering the field, or when they submit their changes?

If you disable or hide this, it makes the whole form pointless, as people won't be able to do what the form is asking for. What are you trying to achieve with this?

Cloud will be sending the emails. Have you got them to check their spam filters? Can you get them to try to login (try with a random password) and see what error message they get? If they get a simple "password wrong" type error, ask them to try the password reset method?

You want a link to another page on this page. You initially said you wanted to replace the "other request" option in the list with your link. The "other request" option is an entry in a list of request types, it is not a link. But you don't want it, so Action 1: Remove "other request" from the portal list of request types…

This is entirely up to you. Most people would archive spaces that are no longer of much use, but they don't want to lose completely. This may happen when a product goes out of support, an organisation changes structure, someone notices that no-one is reading or updating the space, and so-on. Your policies for archive…

Correct, an empty value in the table = unresolved, any other content (whatever it's called) = resolved If you follow the stuff I wrote above, you will fix most of it, but you will be left with issues with "do not use this" as the resolution. You may want to run a search for that to see the extent of the problem with old…

The issue history for each moved issue contains a record that names who moved it, but there's no direct reporting in Jira for this. You'll probably want to grab a list of moved issues over REST and extract the user's names from it.

What did "Hugo" want to know about your Jira when you "enabled" it? (Bear in mind you have not explained what Hugo is, so, although I know a couple of projects involved in the Human Genome Organisation do use Jira, I can't be sure you're even talking about them)

That's correct, if you edit the board filter, you can exclude the bugs. (Rather than "and issuetype in (story, task, sub-task) They won't show on the board or count towards your sprints if you do that. It's not a case of switching filters, you need to use separate views (boards are one type of view) - the board filter is…

You would need to filter them from the board. They're not part of the sprint, clearly, so you shouldn't be including them in the sprint data (i.e. board) What type of project are you using? (Look to the bottom left of the project display for "team managed" or "company managed")

How are you representing your distribution group in your user directory? That's quite a convoluted question on its own. Confluence, somewhere, has a list of users and groups in a directory. On Cloud, that could be an internal list driven by Atlassian accounts, or Google accounts, or it could be via Atlassian Access, backed…

Ok, that's not how Sprints work. You get "counted" when you complete the story, not when bits of it are done. If an issue rolls over sprints because Dev finishes but QA did not, then the issue was not finished and you don't count any of the effort in the first sprint because you didn't meet your commitment. Velocity is…

The Confluence REST API sits and listens to the outside world. If you prod it with a REST call, it will process and respond to your call. Pretty much the same as "prod a url with a browser, a server will give you a web page back. Even if it's just a raw text error", you'll get something the browser can show. The REST API…

Ok, I suspect you've had an inexperienced admin make an understandable mistake. You should never set the resolution to unresolved, it should be cleared out completely. Jira thinks "resolution empty = unresolved, resolution has any value (including "unresolved") = resolved" So, if I am right here, the fix is (as an admin):…

So not a request type at all, but a link to another page. You should remove the "other concerns" request, and then customise the screen to have your link. Natively, the portal does not have a way to do that, but you might be able to do it with refined themes.

That's not really what the summary is for. If you're classifying issues under a product like NIKISA, you probably should be using a select-list, component or possibly a label for it - these are a lot more reportable than a fuzzy search of the summary, and, more importantly, are a doddle to rename globally (without it even…

>n which the resolution is set to 'Unresolved'. Ok, this may be an interpretation, or it may be the root of the problem. Could you look again at the workflow transition and tell us exactly how the post-function that sets the resolution is described? Is it literally "resolution will be set to Unresolved"?

They don't have read, let alone write. The database exporter uses the REST API to read it indirectly (and it could use the REST API to write as well, but I'm not sure that it does)

Confluence doesn't really have anything that maps arbitrary links embedded in content. Uses of the Confluence links, url links, even Jira macros (and other macros that link to other systems) tend to be embedded rather than mapped. There are some macros that do some navigational help - an obvious one would be the "related…

Ok, that rules out half of the possible problems. It now sounds a lot more simple - your board has a load of columns that are not mapped to any status, and all your status are clustered into one column. Could you check the board configuration? Specifically the column settings.

Have a "deployed to" field that holds a list of environments? (And ideally have it automatically filled by your deployment process)

That is odd. I would try going into Admin -> Issues -> Priorities and checking the sizes of the icons (try downloading one and re-uploading it)

What does the rest of the error say?

Do you mean your usage of old and new systems with your account, or do you mean that you are currently the owner of these systems (paying the licence, named as the technical or billing contacts on them etc)?

You don't really give licences to individuals, you let individuals into your systems (it's a pedantic point, but it makes the following text a lot easier and shorter to write) Atlassian systems allow people in via groups. These are set in the global administration area, and most people go with the defaults and have really…

Do you mean when the user selects a value on-screen, or when they create/edit an issue that has a certain selection made?

Depends on what you mean by "decommision". If you mean "delete", then no, you can't report off things that are no longer there. If you mean "stop people using the board", then that would normally be done by removing permissions to use the board. Only the people who still have access will be able to report on it. If you…

So, the question we need to ask now is "How are you representing these work groups in Jira?" Before we can help you search for something like this, we need to know how you are representing it in the data.

Yes, when you click "other concerns" it will take you to a new page so you can write about your request.