Comments
-
No. The best you can do is an active/passive failover, which means downtime while you fully shut down the dying node and bring up the failover node.
-
It's the same on Cloud. To restore a deleted issue, you have to * Restore a backup that contains it to a development Jira * Find the issue(s) to recover * Work out the best way to copy them back into the main Jira which could be* Partial entry by hand * Partial entry by import * Partial entry over REST * Merging (long and…
-
Same in Cloud - that part has not diverged from server yet (although Jira 8 is getting personal notification controls)
-
That's not a lot of good really. My guess is that they're probably not fixing anything, they're just rebooting it. To fix it, they will need to read the logs to find out what errors occur at the time it fails. It could be the same thing every time, or you might have several different log entries with one root cause, or you…
-
No. A very big part of high availability is effectively "clustering" - two or more servers doing the same work so that if one fails, the other can pick up the sessions people have with the dying one and carry on. Another big part of it is having all nodes looking at a single source of data. Jira Server does not cluster.…
-
When you upgraded from 6.4 to 7.9, did you follow the correct route, and go 6.4 -> 7.0 -> 7.9?
-
This is an old thread, and also unclear from what looks like edits and removals. Rather than try to dig stuff up, could you explain what you think the "bug" is here?
-
To add a status to the workflow from a board, the workflow must be "simplified". This is a flag that only an administrator can set. When an administrator gets the "Software Simplified Workflow unavailable" message, it means that they can not set that flag because there is something in the current boards configuration that…
-
Log in as an admin and go to the admin sections (any of the areas in the cog/settings icon will do). Use the admin search to find "behaviours", and it will be in there. If you do not find behaviours, then you do not have ScriptRunner, and it is some other add-on adding the *.
-
I feel part of what I just edited into that answer might be useful. Especially if the prose were improved!
-
I just pointed a new chap who wrote https://community.atlassian.com/t5/Git-questions/Help-The-tags-are-meaningful-can-anybody-assist-me-plz/qaq-p/894684 to the welcome centre. It struck me that the welcome centre could benefit from more content, although the articles in there already link to most of what I'd expect,…
-
The community has recently started a "welcome centre" area which is well worth skimming for useful articles. https://community.atlassian.com/t5/Welcome-Center/gp-p/WelcomeCenter It is low on content at the moment. In my opinion, it should be improved by including directly some of the "how to write good questions" write-ups…
-
You have to remove whatever is granting them access to the projects you do not want them to see, and then grant them access to what you do want them to see.
-
You can upgrade Jira Core from 7.1 to 7.12 in one step, no need to go through other versions. I'm not sure where you are getting that error message from though, it doesn't look like a download error.
-
That sounds like one of your admins renamed the field accidentally, then put it back later.
-
Natively, they don't. You have to reconfigure to allow it.
-
Are you sure you are looking at the right field configuration for the project and issue type? The field configurations are the only way plain Jira puts the * in place and makes it mandatory. If you are sure, then you have made it mandatory using a add-on like the Behaviours module in ScriptRunner, and you'll need to…
-
What add-on are you using to provide the "execution set" functions?
-
Each server has a separate set of users as far as licencing is concerned. If you have an account with access to all three systems, then it consumes a "seat" on each of those three systems independently.
-
"Discussions" don't have answers or likes.
-
You will need to talk to the people who administrate your email to find out what the email server is called!
-
Have a look at the workflow for the issue type in the project. The "solved" button is actually a transition from one status to another. Go to admin -> Screens and add a new screen. Put the field you want the users to put data in on that screen. Now edit the workflow, find the transition, and add the screen to that…
-
Resolution. It is nothing to do with status. Issues without a strike-out have an empty resolution. Issues with a strike-out have a resolution set. The resolution could be any string. You'll see things like done, fixed, won't fix, duplicate etc, and less often, more unusual words like prescribed, penguin, darth-vader. The…
-
It is the only way to do it sensibly. There are add-ons that help, but you usually end up with people asking why they can't create other types, people who create and then change the type, and people who bypass the options by using REST. This forum software has a nasty bug in it that when a link is pasted in, it sometimes…
-
I suspect your project that is different to the global setting has used a string type field rather than a date. The other possibility is that you have an add-on which is providing the field and that has a different format.
-
The SAP integration is irrelevant in your choice of database because any sane and useful integration will not be done via the database. The technical recommendation for Jira is to select from Postgres (best), MySQL, Oracle and Microsoft (worst). But there really is very little between them, and the best recommendation is…
-
It will be kept until you or your users either delete it (recommendation - limit delete permissions to admins only), or a month after you cease paying the bill for your cloud system because you don't want it any more.
-
Jira Service Desk already is "a website for end users to send requests". Just use it as intended, and you'll find it does everything you've asked for, and a whole lot more. No-one here is going to waste their time repeating the standard docs at you, but we will try to help if you get stuck. Please start at…
-
Posting a chunk of log without any context is pretty much useless as a question. If you need help with something, you need to explain what the problem is. (Best I can do with this error is "your database is broken, you'll want to rebuild this test system from a copy of production)
-
In the active object tables in Jira. Add-ons have full access to Jira project data (they'd be pointless without it), but to get to the data for another add-on, an add-on would have to explicitly code to read the other one.