Comments
-
No, What does the project admin see when they go to the project set up and click through to the workflow section?
-
Yes, you can. You may have different technologies available, but one simple sample approach is to build both servers as normal, use rsync to keep the passive system up to date with file system changes (usually, just attachments), and replicate the active database to a passive copy. When your primary server fails, start up…
-
Yes, postgres stores a load of data about the databases it holds in a database. You can, and should, ignore the postgres database.
-
The process you posted originally went: * Export * Upgrade * Swap to new database * Import the old data, so it would have to upgrade and migrate in one step Your comment now says you're doing it in the best order now, so that concern has gone away. What does the SQL in the KB article tell you?
-
No, the permission scheme does not matter. What does the project admin see when they go to the project set up and click through to the workflow section?
-
You could run into problems with users being unable to log in, or text being invisible, and dropped from xml backups. In the future, you may well not be able to upgrade at all.
-
You really need to have an administrator do this sort of thing. They should probably be setting a new base url at the same time you move off the h2 database on to a proper one.
-
Your APEX application should issue REST calls to Confluence to create the pages. See https://developer.atlassian.com/confdev/confluence-server-rest-api
-
That is not what the documentation says. You have two *separate* tasks here. Upgrading a system, and changing the database. In terms of time, you might well be doing them in one go, but there are two processes. Your steps will perform two upgrades. One of them is redundent and the other not the recommended way to do it,…
-
Your database connection is failing, due to misconfiguration.
-
Search for your issues and make sure the "created" field is included in the navigator columns.
-
Yes, it suggests that the screens for the issue you can mouse-over includes the assignee field, and the screens for the other issue do not.
-
That's similar to one of my candidates, although I think yours is better. I suspect it would not be hard to code for "this column has green status in it, do not allow non-green status to be added", plus blocking changing colours from green to other in the status maintenance.
-
You are right, it's not quite the same thing as a command line. When I said command line, I'm thinking of the database command line. For postgres, you usually install the server along with "psql" as a client. It's not pretty, you just run your sql or service commands by typing things and get plain text output, but it does…
-
They'll need a different definition of done that remains clear to the end user (I've got a couple of candidates, but I'm uncertain of them. Most suggestions fail the simplicity test though, including one of mine)
-
I do not know what you are doing here. Your DNS must have changed to allow the url to be found, and you don't explain "add ca cert info" or what the base error is.
-
That flag makes Apache require a valid client certificate. You'll need to create a client cert for the server and enable it in the JVM so that it can talk to itself over SSL.
-
Ah, ok. I don't know, I don't use DBVisualiser. I go with command line mostly. There should be an option for "run plain sql" somewhere in it.
-
Cloud and Server are too different for that to be worth it. I'd use your developer licence to run a dev/test server of the same version as production
-
I don't understand the question. You say you are stuck on the first step and then paste in a query that is the next step. In neither case do you explain the problem you are having. Where are you actually stuck?
-
I suspect they did - they started using the last column as "done".
-
If you're happy with server (because of your security questions), stick with it! There's no need for a migration unless there are significant benefits.
-
Both. And it's a sliding scale in real life - you might be completely Kanban, or completely Scrum, or somewhere between, where you're doing some Scrum ceremonies and processes but skipping the ones that don't help you . I usually look at the processes the team want to do, and the main question is "how do you want to plan…
-
Mmm, it's not an opinion, it's a fact. An issue in two columns is broken. I can't think of any situation where there is any use for an issue on a single board to be "open" and "closed" at the same time. Across different boards, it's fine, and I would be happily defining different boards for different teams, or even for the…
-
Do not bet on functions in Cloud ever making it into Server, and vice-versa. The message at the last couple of summits was clearly what Brandon and Matt have said - they are different products with different audiences, and some features may never cross the gap.
-
When you say "cannot reassign", what are the symptoms?
-
Well, I'm afraid that's completely wrong, because I've loads of people with schemes that work fine. Because the admins have listened to the users. Auto trashing is completely understandable. But also totally the wrong approach.
-
If it can run java and has enough memory to run a decent sized JVM, then yes.
-
In Agile, done the JIRA way, the right-hand column is your "done" column, no matter what the rest of your data might say about an issue. You need your done and cancelled status to be in that column
-
No, you can't convert one type to the other. The closest you can get is re-using the logic, but the two add-on types are totally different beasts. Cloud does not (as far as I can tell) support custom fields in Connect add-ons. I suspect the best you can do is to host the custom field on your own servers, and write a…