Comments
-
The error message is very clear - Jira has no way of knowing what issue type you want to create. Either add a column to the csv with the issue type, or set a default issue type in the STTL project's issue-type-scheme so that Jira can use that
-
At a guess, based on the port, you're running postgresql as the backend. And it has been stopped, so there's nothing to connect to. You'll need to restart it.
-
Can't be done - the gadgets are restricted to 50 issue displays, and even the navigator tops out at 1,000 to prevent performance issues. A glance at one system I have access to shows tens of thousands of open issues, so there's no chance of such a gadget ever rendering. Presenting the users with a potential mass of issues…
-
If you have followed those steps given by Thomas, then your workflow is active. Could you explain either what you did not do in there, or what errors you got when you tried?
-
The ID of the server you're asking for a licence for, I think.
-
1. It's the same code you use to post comments on non-closed issues2. You need an admin account to alter the workflow to allow comments on closed issues (or create a new workflow to use instead)
-
mmm, not sure, it's been a while since I looked at this and it may well have changed. I wouldn't be surprised if the implementation is to allow any active user to be set, as there are cases where it's a valid thing to do.
-
No, it's valid reporters.
-
Anyone who has the permission to create issues in that project.
-
Paid via Atlassian means you pay for it on Atlassian's site and they give money to the vendor - the vendor doesn't have to think about payment routes, having a website to gather payments, invoicing, paperwork etc. Paid via vendor means you give the money to them direct.
-
It's a known bug in JIRA. The workaround is that you need to create a new workflow and migrate to it (obviously, copy the existing one as the baseline though)
-
What does "does not allow me to create" mean? You have to be an administrator, open up the workflow and edit it. There's two editing modes - a "draft" where you have only limited options (mostly changing transitions) and a "full" edit mode where you can do anything. Which are you in?
-
Yes, that is very neat. It's still just the *table(s)* in a page, but it does it really well. (The original poster wanted a whole page, but that's pretty much nonsense, as the data types are incompatible)
-
It's still the same answer - Excel is not an analogue of an wiki page, the data doesn't translate easily. Any converter would be a huge amount of effort to get right as a generalised too, and there's little reward for most of it You could write something that suits you reasonably easily, but you won't find an all-purpose…
-
Not really. A wiki page is generally a large block of unstructured (but formatted) text. How would you translate that into a table? One (variable width) row per line? Per sentence? Skip a line on paragraphs? One column per word? Sentence?
-
Usually means the target issue type doesn't exist in the target project. Check that first - can you create issues of type "task" in the target project?
-
They would recommend doing whatever your DBAs would prefer to support.
-
Either will work fine. The only things you need to consider are load (can your database server handle all of those database schema in one server? If one application is doing something huge like an upgrade, is that going to affect the others?) and the fact that if you need to do maintenance on the database server, you'll…
-
You'll need to find or write an addon to do it.
-
You need a new custom field type to do that. The built-in "number" field is a floating point and it can't be changed.
-
No, you haven't missed anything obvious. Your choices are to do it by batch, or get a backup/export of everything and extract your data from that xml (potentially complex)
-
Yup. Every client I've had who has had performance issues has been able to demonstrate that one of the problems is people doing large excel downloads. It's the impact on other users that is the problem (people are happy to wait for a slow download). 1000 rows seems a little arbitrary - in larger systems (in terms of user…
-
I have a feeling Atlassian may have blocked that option in OnDemand - there are very good reasons for a limit of 1000 issues.
-
It already allows vastly more than 20 bits. I'm not sure what you're asking for here.
-
Third option is to write a plugin to provide your own custom-field-type - that would be similar to Jobin's option 2, but isolated from the other fields and a discrete package (you'd need to worry about upgrading it when Jira is upgraded, but it wouldn't be in the core of Jira)
-
Click "create issue", select "task", done.
-
This is exactly the sort of thing your developer licences are for. Go into your my.atlassian account, find your full licence and look beneath it - you'll see a link to "developer" licence. Use that during migration, then when your new production system is fully working, put your production licence on it.
-
Yes, it's listing them by default because they are there. I suspect you've also set your workflow scheme to use that workflow as the default for all issue types. It is just a flat "look at all the issue types in the system", because they *might* be in use. Simple trick though - look at the numbers next to the issue types -…
-
Install a terminal so you can get a command line, install JAVA and then install the Linux versions of the servers. Now, bear in mind that tablets are NOT designed to be used as servers, so you should expect to run into issues...
-
WAR distributions were deprecated and removed a couple of versions back. You should be ok with JIRA 6.4 as per tag - see https://fr.atlassian.com/software/jira/download-archives but past that, there are no WARs