Comments
-
The admin who built the workflow has added (2) to the end of the transition names for some reason. Best guess is that the workflow already had transitions with those names, which blocks duplication, so the admin added the extra text to distinguish them from the originals (stretching the guesswork - they probably got rid of…
-
I'd raise this with Atlassian OnDemand support - I suspect they'll say "no", mostly because OnDemand runs on PostGreSQL, but they might not.
-
Export everything to xml and import the single project you need...
-
You can't. You can export everything to xml and then import a single project from that (although it's still going to "disturb" the test system)
-
No, it doesn't log anything. You could try plogging through your access logs, but that's a bit hit-and-miss. Best you can do is look at who had permission to do the delete! I think logging is improving in 6.2, but I've not really looked at it in anger yet.
-
Then they're not sub-tasks. Those are link types that are not off-the-shelf, so they've been added by an admin, and they're frankly meaningless because they don't define sub-tasks. They are links, and they do define a relationship, but it's not parent/child, it's parent/parent with a misleading name.
-
I think you've misread it - it's for all sub-task types. Doesn't matter what they're called.
-
There is a built in condition for "prevent this transition if any subtasks are in status". Try that one.
-
Or... what Thomas posted before I got there, too
-
Set the correct URL under admin -> system -> general configuration It should be set to the url your users will be accessing the system under. A lot of people run Atlassian stuff behind proxies, but that rule stands - your users will be using a proxied url, so you set the base url to the proxied url, not the url of the JIRA…
-
It's worth mentioning, because it could be the problem in a lot of cases. In this one, it probably won't be, as the log says it's something going wrong well before any SSL is done, but that doesn't completely rule it out.
-
The error you've got is about something going wrong in the installtion, not SSL. I would drop the server you've now got and try getting a 7.3.0 empty install running before importing the data.
-
I'm afraid not. In most cases, it really does need you to restart Confluence. There is one thing you can try, but I doubt it will work - disable the Team Calendars add on and then re-enable it after a short pause.
-
So the JIRA macro worked. Good news!
-
What do you mean "link to a custom field"? You can draw JIRA issues (and hence their data) into Confluence with the JIRA macros that are built-in.
-
It should automatically use all the same users, although you might want to check their group membership and add them to new groups (e.g. confluence-users)
-
Well spotted, the name is jiradb.script, database.script is Confluence. Very sorry about that.I'm not sure that the installation is less "user friendly", it used to be messing around with files and setting things up. Now it guides you through it, and you only get problems like this when you've crashed out part way through,…
-
Ok, we can work with that!The HSQL database is a little different to the others. Stop JIRA first, then go find the file called "database.script". It should be somewhere under the "home" directory for JIRA (possibly under database, but it depends on version, and I'm not that familiar with the windows installations)Take a…
-
It's assuming that you know what database you pointed JIRA at when you set it up. A mostly fair assumption - which one did you choose?
-
Sounds like you'll need to reset the admin password. See https://confluence.atlassian.com/display/JIRA/Retrieving+the+JIRA+Administrator
-
Could you explain what you mean by "Quicklink Rapidboard" or "Quicklink dashboard"? And how are you doing the "shortcuts on dashboard"?
-
JIRA doesn't have field level security. Natively, you have no options. You could try the field security add-on from Quisapps
-
I would Create a filter for "open and assigned tasks" (by which, I mean the issues you're interested in, not specifically who they are assigned to. Although, you might want to do that later - include a list of "assignee is A or B or C") Create a Dashboard, and add a simple "filter statistics" gadget, choosing your filter…
-
Export all the data from production, get a clean JIRA running and import the data - that's the most simple route, but it's only suitable for smallish systems and there are other options. Depends on the size and setup you've got.To get the database online, all you can really do is restart JIRA. The HSQL stuff is part of…
-
The error means that there is a problem connecting to the database. This is usually a networking error or something has taken the database offline. However, in this case, you appear to be using HSQL as the database. If this is the case, then there are other possible reasons - another program opening one of the database…
-
No, that's why we're looking at users - the internals won't do this, but the users can.
-
It looks like one of your users has created a search for "all issues with comments in a long list of projects". You should ask them to stop
-
Yes. You can even do it by issue-in-project too, but I'd concentrate on getting it right per project first. Have a look in the documentation for "field configuration" and "field configuration scheme" - you'll need one of each for each project.
-
There isn't really a "manual" for JIRA, there's a big pile of documentation and guides. What are you hoping to gain from a static download? Bearing in mind Atlassian are updating the docs almost constantly.
-
Again, check the csv is mapping the issue type correctly and consider adding a default issue type. The error is very clear - it is not able to map the issue types you've provided, it's falling back on the default in the scheme, and you haven't set one, so it's stopping. You might want to try reading the log file - that…