Comments
-
No, you're wrong, but I think you've misunderstood me. You do NOT need Fisheye and Crucible to "support" a database in order to get them to work with it. My experience which lead me to say "any database with JDBC support" was specifically for running Fisheye on a non-supported database and it worked back then and is still…
-
<sigh. Lmgtfy> http://confluence.atlassian.com/display/CRUCIBLE/Supported+Platforms Only your 5th question isn't answered there. I'd also point out that you can run it on non-supported platforms - anything that runs a JVM for the application and any database with JDBC support can be made to run Atlassian apps, but the…
-
Depends on what you've downloaded. If you're on JIRA 6 or lower, then Service Desk is an add-on, which you can install via the plugin managager. But, it's more likely that you're looking at JIRA 7, where Service Desk is a full Application and available in two ways: * As a standalone installation. That installs JIRA with…
-
I'm sorry, that doesn't make any sense at all. I'll say it yet again, you really do need to explain what you expect the calendar plugin to be doing (ideally by telling us what you are looking at in the documentation and what you are seeing in your installation)
-
What does the documentation say?
-
Why are you expecting to see it under "projects"? What makes you think that?
-
Ok, where? (If you've tried to attach a screenshot, I'm afraid Answers seems to be a bit flaky and not always upload them - just pointing at a screenshot in the docs would be fine)
-
Right. 1. Follow the documentation 2. Why are you installing something when you don't know what it's for? 2. What are you expecting to see?
-
You said you'd installed it already, so I don't know why you're asking for that part. As for how you use it, you shouldn't be installing stuff for no good reason - you should have a reason for installing something, which means you should know what problem the plugin is solving, which means you should have selected it based…
-
WHERE can you not see the plugin? For the third time, what are you expecting to see?
-
I am afraid that is still a completely useless statement. You need to tell us what you are expecting and what you are getting. Please, we cannot help you unless you tell us what is wrong. What you're saying here is like saying "I want to drive somewhere" without telling us if you have a car, the car has broken down,or…
-
Ok, so it's installed ok, that's good to know, rules out the first set of things I'd usually ask about. "I cannot work on it or see the plugin" still doesn't help us much though - what are you expecting to see? (Trial version is irrelevant - the only difference is in the licence)
-
"unable to use" doesn't tell us what you are seeing or what you have done. We can't help you without knowing what you're doing and what you expect to happen.
-
All public releases by Atlassian are "stable" (with a couple of exceptions which they remove from the download list) Generally though, people will avoid a .0 release, because it's quite common to find a number of edge-case issues when a release goes out to the wider world, and a .1 usually arrives quite quickly. I would…
-
A board is a view of a set of issues, and is effectively built off a filter, which you can easily change. Create your project, then go to the board and look at the general configuration, where you'll see the board filter. I'd expect it, from what you've said, to say something like "project in (A, B, C) order by rank". Just…
-
I'm not sure that'll work - I think the Jira suite utilities can only copy between fields of the same broad type (text -> text, date -> date etc). In this case, you'll be copying Version -> Label. I do have one reservation about it as well - version names can have spaces in them. Labels can't. So I have a horrid feeling…
-
You need to find or write a listener that will pick up any events that are fired by changes to the issue, reads the event for the change of version, and duplicates the version information into the labels field. If you need to write one (I'm pretty sure you do, I'm not aware of a plugin that provides this already), then it…
-
Is there a reason you are not using "export to xml" in your HSQL installation, and then "import from xml" in your MySQL installation? It's easier, safer and supported by Atlassian...
-
I'd like to see Epic of Epics supported better, it's quite useful (although it doesn't need to be anything more than a logical grouping/link)
-
In the basic theory, Epics are huge overarching pieces of work that are likely to rattle on for quite some time. They're not really items you work on directly, they're more for grouping stories and tasks together so you can plan. Stories should be completed within a sprint, and the whole of Agile works on the basis that…
-
I tldr'd the bit on "coffee" in your essay (because I've not decided coffee is the best way to do anything I need to do yet, and I sort of like drinking the nice Klatchian stuff rather than coding in it), but the rest of it was a huge pile of "yup". As Davin says, the documentation feels wrong to me. I can follow a lot of…
-
Your "customers" can see the portal and the items they raise, or are included on. If you want them to see more, then yes, they need to sign up as a full JIRA user. Although, if you allowed anonymous access (read only, of course) to projects, they'd also be able to see the project that way.
-
Ah. No idea, I'd ask Pivotal about it. There's no harm asking here in case one of us knows, but when looking at software outside the Atlassian suite, it's generally better to ask the community for that software first (and the vendor, of course)
-
What pivotal tracker plugin are you asking about?
-
It's https://support.atlassian.com
-
I really don't know off the top of my head. I've not looked because shorer field names is the right answer. However, you've probably got several templates to edit, and you can't do this in a plugin, you need to amend the core of the stuff that handles issue-view, the navigator, and everywhere else that long field names…
-
Yes, that's what I mean by "code" - you need to amend the templates. I'm not sure which ones (and it may be different depending on your version of Jira, even if I could find the right ones in my version), and it's very possible that by amending them, you'll break something else. For example, if you make the field name…
-
No, it needs code change. Generally, if you've got a large field name, you should simplify it and move the (probably unnecessary) bits into the field description.
-
Possibly. You'll need to define these compliance rules before we can answer the question.
-
I've done 5.2 to 6.4 a couple of times before, and it worked ok, but I've also seen it go wrong and we reverted to doing 5.2 to 6.1, then 6.1 to 6.4. That time it was based on an add-on with some quirks, but you won't find out until you test it.