Nic Brough -Adaptavist- Expert

This translates to "QS Responsible person", which does not look like a standard Jira role (neither a project role nor a dynamic role), so I would guess that it is a custom field one of your admins has set up.

No. You need to understand basic authentication principles. I have a load of passwords that will not enable me to log in because the site has gone, I've lost the other half, thirds, or quarters of my authentication details, or been locked out for some reason. "we have a password so we can log in" is not true. You need all…

Click "configure" on your board, or dashboard.

I think it's important to understand that Jira Classic and Jira Next-gen projects are very very different things and handle things like custom fields very differently. The custom fields you see in Classic projects simply do not exist for Next-gen, they're a different structure, a different table, and hence different…

Yes, it's telling you exactly what the pronlem is. This project is not configured to allow you to create sub-tasks. Your admins can change that.

Sounds like your browser is struggling with the javascript and processing Jira is asking it to do. Jira is not light on that, but neither it is heavy compared with some. Have you tried a different browser? Or a more modern computer with enough power?

This will happen to date-only fields, they're stored as "d/m/y midnight" in the database. Could you check the exact type of your custom fields? Do they say date or date-time (under the field names when you go to Admin -> Issues -> custom fields)

An Epic Link field can only contain links to epics, so you do not need to worry about the second part of your question. For the first part, SR can now do validators, and yours could be as simple as "epic link is not empty", but you could also consider making it a mandatory field on stories using core Jira functions (the…

This is a function you would have to build into your browser. A web service does not have a say in creating local directories.

Generally not the right reason to trigger transitions, but it should be possible. You will need to look at Automation or Scripting apps. A glance at my usual library of scripts makes me think a listener for Cloud Jira could be built to spot changes in your custom field, work out what transition to execute and do it. But it…

Last time I used Axure, the prototype field was a custom field type, so you could go to Admin -> Issues -> Custom Fields, find it and go into "configure", where you should be able to change the "context" from "global" to "a list of selected projects" I haven't got access to that system any more, but you might want to try…

No. Jira does not have a severity field natively (the misuse the severity field sees in Bugzilla is actually one of the reasons Jira was written - to get rid of it), and even if you add one as a custom field, it has no way of knowing that you might want to do strange things like that. Linking an issue to another has no…

It depends on how you set up the two LDAP servers, I can't tell you much about it, but I understand it's possible to have two nodes that are equals.

This might have to go to Atlassian as a full bug-report, for your version of Service Desk - I cannot replicate it at all (4.13 for what it's worth)

You will need an app to do this for you, or enable you to write the required code to do it. Have you got a tool for this yet?

This is absolutely not what story points are for, and focussing on them is completely the wrong thing to do. Trying to do a mathematical quantitative or qualitatvice analysis on this is mostly going to be a waste of your time, because story points are not for this. If you insist on thinking this is a problem, then the…

It's simple stuff for me. Sometimes it's * a decent cup of tea * when something I cook works out as well as I had hoped instead of as well as I expected * finding a new thing (Last weekend, I found Nogroni - not quite as good as a Negroni, but still rather good and 0% by volume instead of 30ish) * the look the cat gives me…

Unfortunately, I'm afraid you are a bit stuck at the moment. Boards only handle fast with fewer than 500ish active issues on them. I don't know of any way to improve that.

I'd guess you are on Jira Cloud in a Next-gen project, which does not have this function.

It usually means there's something in your browser cache causing a login loop. Try clearing the browser cache (at least for all Atlassian related stuff) and try again. You may also need to rid it of cookies from Atlassian too.

It depends on what you mean by "account". If you mean you have an Okta/LDAP/some-other-directory server handling your users, then you could say that you're using one account in there. But in those two Jira systems, whatever directory you are using, they are separate "accounts". Each Jira will count the "account" against…

You will need to read the application (and possibly server) logs to see what is going wrong. Start with the <jira home>/log/atlassian-jira.log file, that's most likely to have captured the fault.

That looks like the status colour is grey, not that the button is greyed out. What happens when you click it?

"An error" tells us nothing about what the problem might be. Best we can do is say "try it again", and possibly "ask the vendor" (and in both cases, you'll need to give us, or the vendor, the errors and exactly where they occurred)

I think you might be misunderstanding the boards - they are not containers for issues, they are views. An issue does not go on to a board, or move off it, an issue is selected for, or not selected for a board. When you closed the sprint, this changed something on the issues in the sprint that meant that they were no longer…

If this a true Server licence (and not Data Center), then yes. The licence is "perpetual" - you can continue to use the server exactly as you do now for as long as you need it. After that date though, you will not be able to upgrade to newer versions, and nor will you be supported. But it will still all work. The only…

You can download it from your my.atlassian.com account, assuming you have a qualifying licence and agree not to share any of it.

The "message field" from the Jira Toolkit may be able to help - you give it a static message, and then you can put it on view or edit screens (edit screens = edit, create and transistion for this purpose) and it will display that text. As it's just a custom field as far as Jira cares, you may be able to use it in Dynamic…

The most simple way to fix this is to fire up a browser with two windows or tabs. Log one of them into your Atlassian Cloud Jira, then retry the application authorisation in the other tab.

This usually happens when you are doing https via a proxy (like Apache or Nginx) and you have not configured the Jira connector to the proxy correctly. Check that the server.xml file in Jira contains the scheme=https line (and the proxy name and port), and that you are not trying to use Jira with an http connection in the…