Comments
-
Ok, there are two things that might be happening here. First, you've given it the wrong password for the username you've tried to log in as. The failed login then gives an additional error. Second, there is something wrong with the user directory set up - you give it a username and password, but Jira can't connect to, or…
-
In Scrum, the fix version means "the version we plan to fix it in". That's what they stuck on the issue, but the decision was made to go for 7.10.0 instead, and no 7.9.3 was built. You'll need to go to 7.10 or above.
-
It's because your account does not permission to see the issue. Could you show us the permission scheme for the project the issue is in, the header of the issue and the security scheme for the project (if any)
-
This means your Jira server can't reach your email server. You'll need to check the route between them, looking for firewalls and security policies.
-
The community here can be quite quick, but there's no way we can answer as fast as <any search engine on the internet> Please, at least *try* to look for yourself before asking. You'll find https://confluence.atlassian.com/adminjiraserver/switching-databases-938846867.html on the first hit.
-
Where is "Release"? And when we get there, what "dropdown"?
-
There is no way to hack the layout code on Cloud. Your only useful option is to stop trying to use botched work-around data. Ask your users why everything for the field starts with <pointless rubbish that should be elsewhere> and why they think this "works". What is the problem they are trying to solve with "SAP -…
-
It sounds like the account is not been allowed to mark messages "read", so it has no choice but to try to delete. What does the log file on the email server say Jira is trying to do and what it achieves (or not)?
-
Without much of an actual question to go on, all we can do is tell you to start at https://confluence.atlassian.com/bitbucketserver
-
Heh. No. Extracting the full issue data for one issue could be hundreds of joins on SQL. The database is the worst possible way to try to ask Jira for data in most cases! Consider scraping it via REST instead - you can ask for issues (or a set of issues) and get a nice clean simple JSON representation of each issue in one…
-
The standard minimal setup for an emergency standby like this is * A copy of the server on a remote site, with Confluence installed, but not running. * Database replication set up so that production data is replicated over to the emergency site. * Attachments mounted on shared storage, so there is a copy of production on…
-
That's the "velocity" template behind the label - you get that when there's been an error in the back end. Could you tell us where you are seeing this and what you would expect the labels to be? Edit mode or view (or both)?
-
Yes, remove their access via the service desk - that's the point - the service desk is giving them access because that is what is designed to do. Or disassociate the space as the Service Desk KB. You also need to check that there is no access for "anonymous" users in the space config.
-
You do not need to upgrade the licence. A licence gives you the right to use any version of the software released before the end of the licence, they're not tied to versions of the software. However, if you are running an upgrade of an existing install, there's a couple of problems with what you've said here. You should…
-
See https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html and https://confluence.atlassian.com/adminjiraserver/migrating-jira-applications-to-another-server-938846962.html
-
You probably need to re-install or upgrade the Apps that provide the gadgets. Check in the UPM (admin -> manage add-ons) to see what might need doing. If there are gadgets missing that you can't identify, let us know what they're called and we can have a go at finding them. But check the marketplace and docs for them first.
-
Yes, that's correct. Think about the definitions of these things: * Done: The issue is finished with, ended, it needs no further action. * Backlog: A list of things that need doing You should never see done things in a backlog. It's wrong, and makes the whole concepts of done and backlog total nonsense.
-
Yes, you have to remove their access to the Jira portal that is linked to the knowledge base you want them not to see.
-
Ah, you probably don't want to. The problem here is that Scrum does not expect you to estimate on sub-tasks (an item is either done or not, it can't be partially done), and because there's several different ways to approach the idea of people doing it, Atlassian have avoided the question and not coded for it at all. If you…
-
I am sorry, to my shame I can only speak English, and just about scrape a bit of French, German, Italian and Spanish if I read really carefully. Could you translate the two red error messages into English for us?
-
Each one of those drop-downs should be a "cascading select" field in Jira. You can import data from CSV into them by using the structure described in https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html
-
Both. The distributable parts of gadgets (the deployed "code") live in the file system, either as part of the Jira install or in the <jira home>/plugins directory as part of the add-on that provides them. The data for the gadgets, including their config lives in the database. (There's a couple that have config outside the…
-
Our comments crossed over, but "I copied permissions from another team" sounds like it fixed it by granting you browse on the project.
-
I've seen this add-on before, it does not have options like multi-select lists because the list is generated by looking at your labels. To change the options it offers you, you need to add or remove labels from the issues.
-
I am sorry, but this does not make sense. The use of "template" suggests you want to pre-fill fields, but that usually means you've started asking users for fields that you don't really need them to fill in. That is a bit of a guess, but I really do not know what you mean by "to associate issue type" after the first part…
-
No, the custom-field panel in the issue view is a single-column view. You'd have to hack the code in Jira that lays out that panel to get it to display in two columns.
-
Ok, so you either have not got "browse" permission in the project (as described above), or there is a security level being set by an automation or script. Can you eliminate the "browse" permission by re-checking the project's permission scheme? Does it clearly name you or a group or role you are in? If you're not sure, can…
-
"I can't view it" - what message do you get when you try?
-
Yes, the board the charts belong to.