Comments
-
Your question is the wrong way around. It's more about those applications supporting the use of Crowd as a user management system. From memory, there's an addon for Jenkins which enables you to use Crowd for users, but I don't know about Bugzilla - I've certainly not seen it done.
-
You still need to give the system something to put in the summary - it's the only completely mandatory field in the system. Your data needs to go into a free-text custom field, the description or environment, as they're the only three types of field (without add-ons) that can accommodate your data. I suspect the reason the…
-
There is no "restriction" on this really. You're just trying to wedge too much into the wrong field. The field is limited to 255 characters, deliberately, as it's supposed to be a summary (meaning short description of what it is). If you want to amass overlong strings into a field, that's fine, but they're not a summary.…
-
One of each "type" I'm afraid you haven't explained what you mean by "type" or "account" really.
-
Click administration. Press . to search. Type in "lic" and it'll probably narrow it down to the available licences you might have. If you don't have that, then I have to take a completely random guess that you are using "OnDemand", in which case, it is in your Atlassian account when you signed up.
-
Then look at the licence screen in Jira. Under admin
-
There's no text files on the licence pages. You need to look at the licence page which will display an end date. You can get that both from your atlassian account and the licence page under admin.
-
So how did you generate the trial licence?
-
Look at the licence page, it will have an end date.
-
Cloud does not allow the installation of "type 2 plugins". You will need to find or write a Cloud Connect equivalent.
-
Yup, that's the one. I'm not sure Roseha is referring to that field of course, it may well be a custom field - I'm sure we'll be corrected if I've guessed wrong :-)
-
I think the "security level" Roseha is referring to is the "security level" field in Jira that controls issue level security. That's a built-in system field that does not have a searcher, hence my suggestions about creating a derived field or editing the gadget to recognise it as though it were a custom select list.
-
Code. You either need to write fields that provide the data hooks that the gadget can read (i.e. they effectively need to be select lists), or you need to rewrite the gadget in a way that accepts that your field is a valid input. I think it's based on the searcher the fields implement - in your case, security doesn't have…
-
Yes, correct, I do. I just don't want to be accused of favouritism or advertising. (Of course, we are really good... :-) )
-
There are Atlassian partners who do this sort of stuff if you don't have the resources - lists at https://www.atlassian.com/resources/experts (in the interests of openness, I should point out that I currently work for one of them) There's a number of good people (not listed as expert partners, but still perfectly capable)…
-
This has nothing to do with Atlassian products. I suggest you ask this in an ACR forum.
-
There is no permission for that. Your group is a start, but you will need to go into every permission scheme you have and add the group into "browse project"
-
JIRA indexes as it goes, so you've got something damaging your index during normal operations. You need to find that and fix it. It's usually a broken plugin or script. Or, as Joe suggests, something is updating your database outside JIRA - you absolutely must find and stop that if that is the case.
-
Cloud can be trialled for 7 days. Server is 30 days. Both offer the full functions of a licenced JIRA.
-
From CSV, you can add by converting it to a jelly script (although I'd prefer to convert it to lines to feed into Bob's CLI, it's much easier), or you could create a dummy project, import your list as though they were issues with assignees, then delete the project when you're done.
-
Have you started editing the workflow?
-
No, that's not quite right, although I think it might be the way I'm reading what's written. * Events are fired by a post-function on workflow transitions. They have nothing to do with status directly. * When you create a new transition (whether it is by adding it the editor, or by using the "simplified workflow" to add…
-
Eh? That doesn't make sense, transition IDs are unique within a workflow and other workflows are isolated so it doesn't matter.
-
Remember that there could be many transitions in different places for that one column move.
-
Yes, sort of. The board is a view of a project or set of projects, and the columns are groupings of status within the workflows the selected project(s) use. The move from "selected for development" to "work in progress" therefore represents one or more workflow transtitions. Each transition fires an "event", which you can…
-
This means a damaged or unreachable database. What did you do to provoke this error?
-
You must give JIRA an issue type (and a project and summary) when creating an issue. Or it does not know what, well, issue type it is, so it can't know what set up to use. I don't know exactly how Crashlytics is trying to create the issue, but you could try setting a default issue type on the project's issue-type-scheme.…
-
Your clients are not using the DNS server, or the changes have not propagated out to them yet.
-
Try "createdDate > -1d" instead The -1d means "go back 24 hours" and you want stuff after that point (There's also some functions you can use which might be useful, but test the > -1d first)
-
Workflows in Jira have * Conditions - prevent users from performing transitions unless they meet certain criteria (e.g. "must be a developer") * Validators - to check the data and prevent the users committing bad/invalid data during a transition * Post-functions - to do things automatically during a transition * there's…