Comments
-
JIRA tries to stop you creating fields with the same name, because it's a spectacularly dreadful thing to do. But there are a number of ways of doing it by accident. The documentation is essentially correct, because you should not have many fields with the same name, and validator code doesn't support it.
-
No, definitely not. A status needs to be a clear statement of exactly where an issue is in its process flow. If you allow the same status to be reused, you simply can't track the issue any more. However, there is a good strong argument for "meta status" to be presented to sets of users who don't need to to know the exact…
-
You can't. It does not make sense to do it either. A status is a label showing you which step an issue is on in the workflow. You can't have the same status for two steps because the entire point of the workflow is that the steps are DIFFERENT.
-
Um, I'm not sure that's quite what I meant. The Status IS the Status of the issue, not so much a taks, but I suspect that I'm just being a little fussy with words. Anyway 1. The colours sound right - I tend to think of blue = needs looking at, yellow = we're doing it, and green = yep, done. So I think you've got a match…
-
I'd break this down a bit. First, I'd take your last paragraph - before trying to create a Jira workflow, map out what you want in the real world. I generally scribble out a simple flow chart, which lends itself to Jira workflows anyway - each circle is a status and each line between circles becomes a transition. When…
-
That's not really a JIRA question - you're getting the issue data from the API call - what you do with it is up to your code. On your difficulties * What is your dev environment doing differently to the calls that have worked and returned your issue data * I'd look for a JSON parsing library for java, and a database…
-
That can be done - REST can be used by any language that supports doing the calls. Could you explain what you are asking?
-
You're not using the default workflow if that is happening Two scenarios could do this: * You're using a copy of the workflow that has been changed (and broken) * Someone has renamed the Closed and Resolved status (and hence broken the default workflow) I suspect it's 2, and if it is, then I would rename them back and see…
-
No. Cloud has a set list of type-2 addons you can get for it, and it's handled by Atlassian and your account. You can't add to that list without talking to Atlassian and convincing them that it's worth it, they can support it and so-on, and if I understood the gist of AtlasCamp recently, they aren't planning to add any…
-
Sorin, not really. The default scheme has some logic and reason behind it, so I don't think Atlassian will ever remove it. I don't think people really mind it being there as a "contains all of them automatically list" either. The problem is mostly that the damn thing gets right in the way because there's no way to stop it…
-
Well, you can swap them to a more simple scheme, but that means you have to get them to tell you what to change all the issue types they are losing too. (e.g. if the new scheme doesn't contain "bug", then change all the "bugs" to "features")
-
It's the proxy settings - you're telling Apache to connect to JIRA on 8443 which is NOT the port for http! Not sure where you got that from - the docs do say to connect to the http port. Try changing it to 8080 in the Apache proxy settings.
-
I always wonder about the mind-set of people who do things like this. They get an email saying "there's a possible problem, here is how to fix it", so they ask a question instead of reading it. Fair enough if they have questions about the instructions, but not bothering to read it in the first place, honestly <shakes head…
-
No, you don't have the option to customise text on OnDemand.
-
That looks like a broken custom field plugin, or tweaked code in the core. Have you got customisations like either of those? Could you try narrowing down the search and see if you can find a pattern when it breaks (e.g. it's only project X, or issue type Y, or when field Z has data)?
-
Hmm. Could you show us exactly what the full query is - literally copy and paste it straight from the JQL box, no edits or tidying (with the order clause and after you run the query and then go back to edit it)? Also, can you confirm that you only have one custom field called "Rank" and that it is of type "Global rank"?
-
Ok, have you made sure the notification scheme says to notify the reporter? And can your user log into JIRA and see the issue? There's nothing hiding it from them?
-
That's not what Service Desk is for, it's only supposed to tell the customer about certain updates. In plain JIRA though, just include the customer's JIRA account in the notification scheme somehow. (e.g. set them as the reporter and send notifications to reporter)
-
Do you have a question?
-
Hmm, well, you said you'd tried viewtracker, and I seem to remember that only tracks numbers. Last time I did this sort of thing in Confluence, we embedded google analytics code in the headers and then referred to our GA account. I *think* Go2Group wrote a plugin that can help you embed the GA code and use the information…
-
Hmm. I think I'd be looking for something else. BBclone is a php based function. Confluence doesn't use php. You could try to wedge something in, but I think you'd be better off looking to do this with something more supportable within Confluence's structures. Could you explain *exactly* what you're trying to do in…
-
I've seen it used with a lot more than 10,000 users (largest one was around 50,000, and I understand that they've grown since I left) and there's no real technical limit. There's a complex interaction between how you use it, the hardware involved and the actual interaction of the users that will begin to cause issues if…
-
Just to add to that - if you set up a project that only you can see, then you've got a "personal issue tracker". No add-ons needed.
-
No. It needs some basic information to identify a user otherwise it can't respond to the right people or control access to the issues.
-
No The point of the Excel download is for people to grab information to manipulate for reports. It's a convenience, and it's one-way. It's not "optimal" to do updates that are not within the dataset you want to change, and a download is, by definition, obsolescent the instant you have it, so you really don't want to be…
-
You'll need to raise this with OnDemand support. I seem to remember previous discussions about it, and people saying "ask support", and getting responses from them. I don't remember a flat "no, we don't do that" from support, so it's definitely worth asking.
-
Make sure the steps field is unlimited text, then check that the "renderer" is rich-text. You'll find text like || header 1 || header 2 |||data|more data||Something| something else| comes out as a table
-
You can only have one base url - you need to make sure that is set to the url you want your users to use (which seems to be jira@xyz.com to me). If you can't access it using the DNS name, then you need to fix your DNS setup I'm afraid, because that's a core problem. Jira will happily respond to incoming requests, but it…
-
This usually means the client is not getting all of the data it needs from the server in order to render it. The fact that one of your offices is ok and the other fails pretty much proves that it's the network in the office where it is failing - they're not able to get all the data.
-
Projects do not contain other projects, so that is not going to work. However, sprints do not belong to projects either, they belong to boards. So, all you need to do is create a new board that includes all your projects, and you should see it reflects all the sprints as well.