Comments
-
Pointing to urls has been discontinued, you now have to upload the icons. Click on "select image" next to "icon avatar" to change the icon, the screen you get from that includes the current list and an "upload new icon" option
-
Mmm, I completely agree with your worries on those to be honest. I don't have a huge amount to add.Keep plugins to a minimum, look for the ones that you *really* need. As you say, many have not been tested at scale in any decent way (there's at least three in the marketplace I'd run screaming from for large Jiras, not to…
-
You'll probably find your issue closed as a duplicate of https://jira.atlassian.com/browse/JRA-3156As it stands, a good recommendation IS to keep the jira admins to a very small group - three or four for most installations. If you think you need more than 10, you have a structural problem.On the other hand, I'd be quite…
-
I've got the same worry. Part of it is experience - almost every Jira site I've been to has started with a project to clean up the mess made by allowing too many administrators. You'll generally find that project leads are ok when limited to their own project (like components and versions) but they will make a total mess…
-
No. Custom field options are set by administrators. Project owners can be given maintenance of Components, Versions and Users. That's all. Atlassian are working on a more flexible model, but it's not there yet.
-
Could you remove (temporarily, of course) assignee and the two custom fields as well?
-
Yes, because they might be a reporter.
-
It's the first line. If you allow the reporter to see the project, Jira has to open up the project to everyone who *might* report an issue. Sorry it's taken a while to get there, you said the users had "no permissions", but there's actually loads there (other than the role ones which tend to be standard)
-
Right. First, go to the project and check exactly which permission scheme it is using. Then, go into that scheme and list here *everything* that has "browse project" rights. Don't try to interpret or explain anything, just give us the plain text of the box on the right (feel free to obscure any names with personal id info…
-
That still strongly suggest you've allowed "anyone" to browse the projects. Then used issue security and/or reporter-browse to hide existing issues from them.
-
Oops, sorry. Also a possibility - you've used a user or group picker in the project browse permission. That has to expose the project to people who might be named there, even if there are not yet any issues that match the criteria.
-
You've allowed "anyone" to see the projects.
-
I'm afraid that's the problem - I had to hand it over to an Exchange admin to debug it.
-
I have a slightly wobbly old memory of seeing this error before, although it wasn't in Jira. The message you're getting is actually telling you that the email server is refusing access to the IMAP folder you're trying to scan. The exact reason, I can't tell you, although I remember the email server logs telling us what it…
-
Generally, it's very odd to put a comment on an issue as you create it - comments are for a discussion, why wouldn't you just put what you want to talk about in the description? Anyway, the short answer is "code". You'll want to find/write a post function or listener that will run on "issue created" and add a comment. As…
-
There's no way you can do this natively. If a user can create an issue in a project, they can create one of any type. You'll need to separate the operational issues, service requests and change requests out to separate service desks
-
No, you need to check the log - I have no access to your logs. Ideally, look at the application log around the time you run the Jelly script. (I know you've pasted a log above, but it's the shutdown/startup log, nothing to do with the jelly). You need to give us the part of the application log for around the time you run…
-
You'll probably find that the application logs tell you the real reason. In my experience, you'll find a message telling you one of two things * It can't write to the temporary area of the disk because of user permissions (the user running Jira), or it's out of space. You should see a complete path and error message when…
-
Sorry, it should be "Field configuration scheme". That scheme tells the project what "field configuraition" to use for each issue type in your project (there's a good chance that there is only one field configuraion in use)
-
Ok, the text boxes have "renderers". If you're using a plain renderer, there's not a lot you can do. But if you swap to a rich renderer, then it'll accept and display wiki markup. You can change the renderer for a field in the project's "field configuration" (note that the renderer only applies to rendering, the underlying…
-
There's a couple of things you might mean here. First, do you mean as part of the text? The rich text boxes have and amongst others. Second, do you mean as a field? As an admin, you can add multi-checkbox fields.
-
Not really, the point of the quick-filters is that they're simple on-off toggles, not something you have to add more to when you try to use them. But you can use dynamic functions in your filters - assignee = currentUser() is an obvious one, but there are others that could help you too.
-
Not really, but I think your question very much hinges on what you mean by "active" and what trends you're interested in. It could get very complex very quickly, because a simple "show me how many issues are being opened and closed" isn't actually useful, until you take into account the number of users and the type of…
-
No, because the status of an issue is nothing to do with an issue being "resolved", directly. It works off the field "resolution" which is independent of status. If you want this to work, you need to change the workflow so that the resolution field is only set as the users go into the status you want to think of as…
-
I don't understand the requirement - what do you mean "using two values"? The point of a pie chart is that it gives you a breakdown of number of Xs that match Y in a given set of data (by definition, you can only use one filter - that's what gives you the data to report on, so I'm even more lost on that). Where would you…
-
I'm afraid I still don't get it - that reads to me, as "project issues" compare to "project issues"? Which is a 50:50 split under all circumstances. If you mean something like "open issues vs closed issues", then you can't quite do it, but you can get close. Do a pie chart on "all issues in project" and select Status or…
-
A link is a convenient visual note for the humans to understand that there is some form of relationship between two issues. They don't do anything other than show some form of relationship (unless you start coding or using add-ons).
-
I don't really understand what you're seeing or where you might be putting the Zendesk reference in JIRA. Could you give us a screenshot, or explanation of what fields are where on your JIRA issues, and explain what is missing?
-
See https://confluence.atlassian.com/display/AOD/About+Your+Data
-
You can't. As it says, you have to be an administrator to create projects. There are some add-ons which allow you to sort of delegate it, but natively, no.