Nic Brough -Adaptavist- Expert

If it's saying "the database is not yet configured", then you have not finished the installation process. You need to complete the installation process (i.e. run it, visit it in a browser and do the things like set up a default admin user and configure the database)

"Without add-on" makes the answer a simple "no". You'll need an app to provide this function.

A newly installed Jira will not have this file until you have completed the set up of it. I have to question why you're looking for this file when you are part way through an installation - there's no possible reason to be messing with it until you've finished the install. What are you trying to achieve here? Not "I want…

This error really is what it says it is - Jira is unable to connect to your database with the credentials you have given it. Can you log into the database directly *from the Jira server*? Or are you checking that with a different machine?

That's correct, only Service Desk Agents can raise and work with issues in a service desk project. But other users can create requests, which are backed by an issue, if they are a customer, and there's nothing that stops a Core or Software user also being a customer.

There is not going to be any fix for this in the code for the foreseeable future. Your only proper fix is to beat up your admins to fix your fielditis problem.

Yes, as above - you have to change them to an issue type that is not going to be removed.

Boards do not directly belong to projects, and hence their permissions and config are separate. So, yes, you can configure a set of boards so that some people can see some of them and other people see a different set. Look at the board configs for the permissions as to who they are shared with and who can see them.

Ok, that looks like a text field. So "Test Number" = "what you're looking for" will do the job, assuming you've put the right text in everywhere.

>A jira ticket(issue type is new feature/task) So you mean "issue"? > A jira issue has one item: Test Number which is placing cases, right? I have no idea. You have not told us what this is (where it is coming from, how it is stored on the issue, or what it is for). I am stuck on what you mean by "placing cases" too, but I…

Repeating the word that has been questioned adds nothing. What do you mean by "level"? 

I do not think it is clear that an Atlassian account belongs to a person rather than an organisation at first, at least until stuff like your situation needs questioning. (organisations can claim and become the owners of Atlassian accounts, based mostly on the emails associated with the accounts). You're not alone in the…

Normally, when I ask for help understanding the situation, I get a lot of slightly different words that add nothing or irrelevant information, but I would love to buy you a pint (or whatever your local way to say "thank you" is) for clarifying everything perfectly for me! Mostly: > Bob's Atlassian account > his email with…

Ok, one down, scan = search. Can you please tell us what you are searching for? "add cases in test number" and "all cases in all tickets" tells us nothing about the data you are searching for, so we can't begin to define a search. Are these things sub-task issues? Are "tickets" Jira issues or does it have a more specfic…

What do you mean by "level"? And "level in sprint"? My only guess is that you mean "rank" - the order the scrum team places the issues in the backlog so they can select the top handful for the next sprint.

Ok, so there are bits of this that are unclear, so I'd like to get a good look at the actual set up. Let's imagine you had someone called "Bob" , with an email address of "bob@somewhere.com". Bob has an Atlassian account, and has become a watcher on ID-240 in Atlassian's Jira. So, where I am missing information: * Where…

So you did not deactivate them from the Jira that is sending them the mail? That means they're still an active user in there. Deleting them from your systems is not relevant if you haven't removed them from the system sending the emails.

Jira does not send emails to deactivated users. The notifications you are seeing must be coming from some other route.

Automated password generation is a security risk - it significantly reduces the security of the password. So you should not be doing this. Even if the APIs support it, don't do it. (Unless it's a very high entropy password that will not be stored anywhere)

Your screenshots could be showing us several things: * Permissions have been changed, or people removed from roles/groups, such that some projects are no longer visible. Permission and user membership changes are the most likely cause of the different assignee lists too * Note, it's not "issue security" - that could…

Project archiving only exists for premium subscribers (you have said you are on standard in the tags). See https://confluence.atlassian.com/adminjiracloud/archive-a-project-1013843066.html for more

The directory gives you the contact details for the partner(s) you choose.

In what part of Jira are you trying to define this block?

The error in this log is a simple network error - the Jira script runs, sends something to a remote service and waits for a response, then completes when it gets one. In this case, there is no response coming back within the time the OS allows for connections, so the script fails. You'll need to look at the remote system…

If "upgrade app" is not there, then the app is already on the latest (valid) version. Or there isn't a valid version for your version of Jira. Your original screenshot is showing a set of fully upgraded apps, so there's nothing to do there. Atlassian support will help you with an upgrade if you run into problems (assuming…

Validators would be a bad way to do this, ugly for the end user, so Jira hasn't got any suitable ones built in. A validator acts after a user has triggered a transition, potentially having entered data that they want to change. If the validation fails, the user will be thrown back to the beginning, which is annoying and…

Mmm, not quite. Your question was about displaying some diagrams, not about what data is behind them. I think you need to start with a look at what you're trying to capture and draw up diagrams from.

That sounds like Tomcat is running, but has not started Jira. It can take a while to load up a Jira system, even a new empty one, so leave it a few minutes. If it is failing to start, then you're into reading the application and possibly application server logs to see what the errors are. The application log is <jira…

You'll want to get in touch with the owner of the repository.

I would download the files from Confluence, and write something in excel that generates the SQL you need from it, and then executes it in your remote database.