Comments
-
No, the key is designed to be set by the human creating the projects because 99.999% of us want to set it to something that hints at the project name/scope. I suppose you could write some code to do this for you, but I'd suggest going with your second idea instead. A really simple implementation could be to create a…
-
What "Atlassian config plugin"?
-
Very good point - the project category is just a project level data item. It's logically irrelevant to issue creation, because an issue belongs to whatever category it's project is in. Bob's suggestion is the only use I can think of - to allow the users to narrow down the possible projects by category.
-
You can include as many projects as you like on a dashbaord, although it does depend on the gadgets in use. A couple are specifically project reports, so you'd need to use more than one gadget to get more than one project on a dashboard, but most report off a saved filter, so you can just select a filter with many projects…
-
YES. It has one.
-
Define a new scrum board that includes the issues you want in the sprint and create the sprint from that board. It's going to get "interesting" having issues in different boards, but there is no other logical way to do it!
-
Ok, I'm not sure that is a lot of use, because a file on the user's machine is probably not going to be on other people's machines, so someone reading the Jira issue will end up with a dead link. (e.g. if you have a file on your machine under c:\reportdata\myreport.txt, then that link is never going to work for me - I'm on…
-
That does not make a lot of sense. What do you mean "link to a local folder"? If you mean a directory on the JIRA server (which, by definition, is not "local"), then how are you exposing or sharing that directory? Or do you mean a directory on the user's machine?
-
It depends on what you're doing. The code to retreive the current mutable issue is different for post-functions, listeners, etc etc etc. Where do you need to do this?
-
Please explain what this has to do with JIRA? (Or an Atlassian product)
-
How are you defining that two issues are "related"?
-
Some saved filters may be affected, it depends on how they have been created and stored. If there are filters that stop working because of a change, your users will see an error message and the owners can easily go correct them. The name of the priorities is a label rather than an absolute in most places. JIRA works in the…
-
That looks like it's a bug in the gadget code. Check that the add-on is valid for your version of JIRA. Having said that, are you on JIRA 7? I seem to remember this add-on coming up earlier this week - it has been flagged as valid for version 7 by the vendor, but not actually tested. It was last compiled several months…
-
Sort of. You can bulk edit labels, but label field suffers from the same problem as all the multiple-value fields when using bulk-edit - if you try to set it to a value, it will not *add* the new values to the list, it will overwrite the existing values.
-
What do you mean by "keyword"? Assuming it's a field, the simple answer is "use bulk edit to set the field to that value"
-
Issue participants sounds like a read-only field that is pulled from other data, so it won't appear on screens that are for editing issues. For the reporter, do you have "modify reporter" permission in the project? The field won't be offered to you if you don't.
-
Yes, that was enabled about a year after the question was asked.
-
Actually, no. Your base url has to match the url presented by your OnDemand account, and that cannot be changed.You can arrange with support to get a new OnDemand account with the new url you want and then export and import.
-
Nothing. The base url is not changeable because if you change it to something other than where JIRA is available, it breaks things (no data damage, but broken links in emails, gadgets not returning data, some links and so on). Your base url should always be where JIRA is running. I suspect what you are actually asking is…
-
One additional point - you have missed an important concept in JIRA. There is no "make field mandatory on screen". A field is made mandatory for the issue type (or all types in a project) OR on workflow actions.
-
Correct, it's an add-on - see https://marketplace.atlassian.com/plugins/net.customware.confluence.plugin.redirection/server/overview# It is also possible to code it yourself in a user macro, but that's a bit of a pain to debug and use reliably compared with the add-on.
-
Try the redirect macro?
-
No. Not without doing a lot of changes to the core code. There are feature requests for this sort of split, which Atlassian are accumulating under https://jira.atlassian.com/browse/JRA-3156 - see/watch/vote-on that
-
Again, why? If you install the main one, you get what you need. There's absolutely no need to be messing with the core. What makes you think you need to install it?
-
That's the link to the source code, not the plugin. I'm not sure why you'd want the core without the main plugin, but to get the core, install the main plugin.
-
There is no "plugin core", hipchat is a standalone system
-
No. You would need to rewrite a load of the core code to do it, and quite probably, some of the add-ons.
-
It's important to understand that "administrator" really does mean "administrator for the system". It does NOT grant you rights over spaces/projects/data, those should come from adding users to other roles/groups/spaces etc. The model of "admin can do anything" is broken and wrong and I'm glad to say Atlassian don't…
-
Use the "default Jira project" as the template - that will pick up existing schemes instead of creating new ones every time.
-
Right, don't try to use the permission validator. It's a hangover from JIRA 1, and does not really work in any useful way. At some point, it's going to go away.There is no way to use the validators in Cloud, as you can't implement any of the "hacks" that you'd need to do it.