Comments
-
Agile and Portfolio are independent of each other, but if you have Agile, then Portfolio needs some access to it as there is extra data (sprints, Epics and story relationships) that it needs to be aware of. You're struggling to find pricing because Agile has been replaced by "Software" in JIRA 7, and all the documentation…
-
I'm not sure what FAQ you're referring to here. The list of versions you do refer to is correct, and the problem you're having is that you have JIRA with a version of Agile (not JIRA, but the Agile add-on) that Portfolio does not work with. You need to upgrade JIRA Agile to the latest version you can use for JIRA 6.4.11,…
-
I've worked in a couple of places that may be similar. I've generally managed to get my way by talking in their language - in my case, they were financial institutions, so I had two really simple approaches. 1) Call the regulator - for many types of financial information, usage of software that is out-of-support can lead…
-
I'm afraid Firefox 3.6 is not supported either by Atlassian coding or by Firefox developers. There are some workarounds for the various problems you are probably enountering, but some involve hacking bits of Jira code some involve turning off features, and many of them need patches to be applied to Firefox, in the core or…
-
> have created a filter that shows filters fir Project, type, status, Assignee etc Filters return a list of issues. They say nothing about the output (other than a sort order which some functions that use filters will use) If you're using a filter in something (like a gadget) that lets you choose fields, then you should…
-
Create a filter for them, and use it in a "filter results" gadget. You can pick out whatever fields you need for displaying progress in there.
-
No, Portfolio is currently an add-on, so it has to be licenced at the highest number of application users you have (If you had 3 Service Desk Agents, 50 Core users and 100 Software users, then you need 100 Portfolio licences, even though your user count is 153)
-
You can use https://www.atlassian.com/partners/search to find a Solution Partner (Yes, I work for one now, but I recommend looking for yourself)
-
Excellent. You should be able to bulk-edit to clear out versions, but a script might be easier as you won't run into any "can't clear it because the issue is not editable" issues.
-
Ok, I've made a mistake. It's been a long long time since I last looked at doing this with priority, and it seems to have changed. You can not remove the default setting any more, so a priority will always be set, even if you hide the field in the field config. Sorry! (You're ok for versions though, you can still blank…
-
Yes, the system still displays content for system fields even if you remove it from the field configs. You will need to blank them out in the issues. I'd filter for "project = x and priority is not empty" and bulk-edit the values to a blank (and repeat for versions)
-
You'll need to code for this one. You need to remove the standard email functionality and implement your own, one that understands the "check box X means don't send email"
-
You may find that existing issues were moved from one resolution to another. They may still be wrong - to fix that, you need to push them through a transition that removes the resolution completely (post-function to "set resolution to <none>" or "clear the resolution"), or you could use something like the script-runner add…
-
You need to remove the resolution from the edit screen immediately, it is breaking your data. Could you please check your setup of the field as well - what is the list of resolutions and do you have "unresolved" on the list?
-
ARGH! NO! You must NEVER add a resolution of "unresolved" to the list of possible options. It breaks your data, quite spectacularly. Ok, that's a bit of a quick over-reaction, as the rest of your question suggests that it might not be what you have done, but you really must check this before you go any further. Go to Admin…
-
It would be nice to have a numbering system of sorts that can represent a plan like that.
-
Not really, the key is allocated at creation and only changes if you move it to another project.
-
The theory is below (stolen from https://confluence.atlassian.com/display/GH/Ending+a+Sprint ) but I've heard of cases where it's not doing exactly that. Seen it a few times myself, but always been able to track it down to a dubious definition of "done" in our more peculiar projects. I am not entirely sure how it decides…
-
A field that is set to mandatory is, well mandatory. The screen is utterly irrelevant - a screen is just a list of fields to present to the user when they do something with an issue. It has nothing to say about the fields behaviour, just that they're there and in a chosen order. If you want to make the field optional,…
-
Pretty much the same. Export from Cloud, get that loaded into the latest version of Server, then merge in all the other server systems (this is not usually a "fun" job, I'm doing it for a client at the moment, and it's really finnicky. You'll find it easier due to some bug fixes in JIRA 7)
-
First, merge all your separate JIRA Server instances into one - see https://confluence.atlassian.com/jirakb/how-to-merge-jira-applications-instances-244352137.html Then migrate the result to Cloud - see https://confluence.atlassian.com/jirakb/migrating-from-jira-server-to-jira-cloud-779160826.html
-
I'm not entirely sure what you've actually done (or why) here, but you need to go back over your configuration, as you've removed the fields you need. For each *custom* field, check that * It has the right context (Global, or valid for that project and/or issue type) * It is enabled in the field configuration * It is on…
-
Think of the types more as templates - they determine the initial layout and default data (including local templates), but once created, they don't really have much effect. The knowledge base flag can be useful if you are integrating with JIRA Service Desk. As for your specific question, I would look at what each…
-
You can't. You need code to do it in Jira, and you can't upload a plugin to provide it, or change the core code in OnDemand/Cloud I think you might be able to stop users entering over-long strings with validators in some of the plugins you can add to Cloud, but I can't remember exactly which ones are available and if they…
-
It will create a copy of your current permission scheme, and then change the current one, fixing the problems it has found.
-
You have not configured the links between JIRA and Bamboo correctly - as it says, go to application links to set it up properly.
-
You don't. Sub-tasks are the same as the parent level issue types - they're all just issue types. If you add 10 issue types into a project's "issue type scheme", all 10 types become available in the project. For the sub-task types, the parent type is irrelevant. Let's say you have a scheme that says * Task * Story * Issue…
-
Start at https://www.atlassian.com/software/jira/pricing
-
Your boss is in a group, probably a default one like "jira administrators". He needs to add you to that group in the user maintenance section.
-
You're going to need code to limit the summary field, although there are several approaches. * Change the "edit template" for the summary field so that it uses html code to limit the user to 100 characters. Whilst this is relatively easy to do, it does mean changing core code in JIRA, which you then have to maintain during…