Comments
-
You might want to explain what errors you are getting
-
No, not a fool. It's a complicated system, and there's loads of different ways to do things. It's very flexible, but that leads to complexity in looking after it, and it's bewildering. Fields and "why doesn't field X appear when Y" is not easy. I trip over it all the time, despite <mumble> years as an admin. There's a…
-
To get fields to appear, you need to check * The screens involved (I think you've covered this - screen schemes and issue type screen schemes etc) * The field configurations (you can hide/show fields here) * The field context (on the list of custom fields, you can say "show field in project X, for issue type Y" and it…
-
You're missing the point - you are going to need to keep restarting your Jira, regularly and frequently. If you've changed the properties file and restarted, then I don't understand why it wouldn't work - it does here on Test, although I needed to do it twice, and that was after I realised I'd put the wrong owner on the…
-
Just don't forget that you will need to restart your production service regularly, before it chokes up the cache and dies. You may also experience odd pages going wrong due to this change (with increasing frequency as time goes on between restarts), although they should be fine if the users seeing them simply refresh the…
-
Bother you beat me to it. I was going to say "you can't do this in 4 or 5 without running out of resources, so you should not really have done it in production in your old version, let alone version 5". Also, you need to restart Jira to pick up the changes in that properties file too...
-
All issues must belong to a project. The closest you can get to this is to create an admin/global project and place non-project issues in there.
-
Oops, thanks Jamie - I've only ever used "in subtaskType". Should have realised there was a similar one for parent types.
-
Um. >as I have 'Bug' issue type as a parent issue and 'Bug' as a subtask as well No, you don't. Probably. Issue names *must* be unique in Jira. I suspect you've probably got something like "Bug" and "Bug." or " Bug" (note the whitespace). If you have really got two issue types with the same name, then you've hacked…
-
Yes, select by issue type. Use "issuetype = A, B, C" where those three issue types are parent types. JQL in later versions makes this more easy: issuetype not in subtaskIssueTypes()
-
It's under the tools menu to the right of the issue. If it's not, then please re-read my answer.
-
Go to the issue and use the tools menu to click "create sub-task" If it is not there then you either do not have "create issue" permission in the project, or your project does not have any sub-task types in the issue type scheme. Log in as an admin to fix both of those.
-
No, you can't use custom domains for Cloud
-
This new url is not as simple as just adding a variable - you'll need to create a plugin that adds the variable url, allows the administrator to configure whatever it is, and then provides the url to non-admin accounts. You'll also need to write all the API segments to expose it internally. I suspect you might be best off…
-
Yes, a Condition stops you executing the transition, and works off current data before the transition starts. So it always passed your code because the current resolution was null. Another option would be to not ask the user for a resolution - instead, use a post-function to set it to "abandoned" or whatever the most…
-
There's a built in "time in status" report - would that help?
-
Because it's possible to select notification schemes that are inappropriate. Some sites I've been to, it would work fine. At most, it's not - most project admins quite happily select schemes that they simply don't understand, and end up spamming all sorts of people (It's not just notification schemes, most schemes are too…
-
People with high enough points can ban users. It's still a couple of clicks away from the landing page, but it's not too far off.
-
I've probably clobbered 50 in the last couple of weeks. Captcha is known to be broken.
-
It's still a public-sign-up system, and it's still a doddle to bypass Captcha. At least the postings are now throttled, so the spammer can't post more than a couple of times before an admin can kill them off. (There's a bug in the permissions at the moment - only admins can ban users, those of us with high karma can't do…
-
Oh, and blocking anything with a link in it that doesn't conform to a whitelist (Again, that rule could be dropped for anyone with >50 karma or something). I suspect the whitelist would be simple - atlassian, OnDemand, and a pastebin.
-
Captcha's aren't really that good at stopping spam any more. I'd like to see some more simple blocks, like "you can only post a question once a day until your Karma is above X", and a similar rule for comments. One thing I've noticed is that when we instaban someone, they get recreated by the 'bot. Something that remembers…
-
Have a look at https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions You can get to the right permission scheme via the project header -> permissions or by going into the administration section and finding the list of schemes and clicking on the one your project is associated with.
-
It's still the same answer - check that this user is "assignable"
-
You need to have "assign" permission and they need to fall into "assignable user"
-
Yes, you should be fine with that. As long as the new 2013 AD servers can be used by JIRA and Confluence - and especially if you are migrating the whole thing - credentials, user lists, groups all the same as 2008, you shouldn't notice any difference. (p.s. I've changed your labels to remove "Cloud", as Cloud does not…
-
Ahh, try the Confluence "scaffolding" plugin...
-
That's the problem, you don't know what PSR means, or what the plugin is. Nor do we, there's too many it might be!
-
Have a look at https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials That contains simple generic tutorials to do searching and logging-in via OAuth. It uses curl to do the calls because that is one of the most clear and simple ways to demonstrate them with a generic but working call. You…
-
It will try to use the licence, but that won't affect your production rig.