Comments
-
So how is your really simple filter limiting the selected issues to just those three projects?
-
Are these fields global or limited to certain projects/issue-types? If they are limited, then your search *must* be limited to the same, or Jira decides to hide the columns because they aren't relevant to some of the possible results. Try a really simple search for only issue-type X in project Y (ensuring that at least one…
-
No, JIRA is "permissive" rather than restrictive. You don't take rights away from people, you give people rights to do things. If they shouldn't be able to do something, don't give them the rights. Your system is probably set up with the defaults. The permission scheme will say "Browse project = role: users". In each…
-
No, all sub-tasks are available to all issue types in your project. You can play tricks with javascript or the behaviours-in-ScriptRunner addon, but those can be bypassed and the javascript is a nightmare to do or maintain, and you need to implement it in several places. You can also deliberately break the sub-task…
-
Sounds like the plugin has not been enabled to me. Check the list of plugins, and try enabling it (or re-installing it)
-
I'd prefer a default of fluid, because it works fine for most of the stuff I write. The ability to do fixed width would be very welcome for the times when fluid doesn't work for me, but that's maybe 20% of my tables at most. I think the main reason for choosing fluid is that I don't want to have to think about column…
-
Can't really tell you much without the error messages.
-
It does tend to lead you that way (built-in filters on project screens are obviously project-centric for example, the quick searches have project first, and so-on), as the general assumption is that most users tend to have at least an idea of the project first. But it really doesn't rely on it. One trick I've seen is…
-
Very much so - Jira has completely open queries thant can be as simple as "Field is X". So if you've created a field called "products", you can search for "products = car" and it'll pull issues out for the report from any project where car was selected as the product. The search is a great deal more powerful than that,…
-
Or the script runner if you're on Server
-
When you say you're using JIRA 7, do you mean Early Access (not suitable for production use) or Cloud (where you can't install that addon anyway)? As far as I can tell, the add-on has not been updated for version 7 anyway, so you'll have to wait until it is.
-
The only thing I can think of is, well, what Martim posted already. You may have documentation set as the default theme.
-
Ah. System admin does not give you rights in a space - you need to check those separately. Specifically, do you have space admin?
-
What rights do you have in the space? And what theme are you using?
-
I don't think it's possible without plugins, precisely because of the way it works. Jamie's script plugin will do the job exactly as described if you don't want to use JEMH. But you'll need to install that instead.
-
Hmm, I was going to say: I'd look at adding a dummy jira user with that email address. Add that to the notification scheme and Jira will send an update email to the address, and create a new issue. Then I remembered: Most of the email handlers will spot the existing Issue Key in the subject, and attach the "new" email as a…
-
If you can view an attachment, you are downloading it. That's how browsers work - they have to download content in order to show it to the user.
-
Nope. The templates are literally one-off processes, the information about which one was used is not recorded. (A lot of us bury hidden data in our templates to stamp it with the template name. Not ideal as the users can remove it, or modify the space/page so much that it it's unrecognisable from the template, or even turn…
-
Standard function, just add it to the view screen. It'll be displayed when there's data in it.
-
No, a project can only contain issues with its key. A main point of the key is that it tells you what project the issue belongs to. You can still use the old key - searches and the direct url for the issue will go "oh, that's moved", but that's it. Some places use copies or parallel issues, so you have one in the service…
-
You can't on Cloud - you need one of the extensions that provides calculated fields (Script runner, JJupin etc), but you can't use them on Cloud. I suspect you could write a Connect plgin to do something, but I've not tried Connect in anger yet, so I'm not sure.
-
And don't forget to take a full backup BEFORE running any SQL. This isn't so much of a workaround as a bit of an unusual hack. It does work though, just bear in mind you can't go back when you've done it.
-
It's not possible to do this conversion in the UI, so you must have been hacking the database. You need to explain what you're done to do this conversion.
-
Yes, that's what I meant by the auto-complete for those fields - the renderer for them is doing the work. It's annoying that components is effectively nothing more than a multi-select (when it's on-screen anyway), and it has that renderer while the custom field does not. The downside of using components to do this is that…
-
I don't think you need to consolidate all your projects into one? The field will work across all issues if you want.
-
Mmm, I'm still hoping to get the labels/components/versions type-ahead implemented for multi-select fields. That would solve it, but it's not there yet.
-
Ok, to start with the question list. 1. Not easily, you need a bit of advanced config to do this 2. No. The whole point of the field type is that labels are free-format labels to arbitrarily group issues together. 3. Yes, absolutely 4. You can create many custom fields of any type. Labels is a type and there's a single one…
-
It's "a la carte" as you suggest. However, it may be worth talking to Atlassian partner companies - many of them do bulk licensing and a little bit of discounting
-
I'd like to scribble "integration" on that as well. Confluence talks to other systems relatively easily (obviously, it's very good at talking to other Atlassian products). Other wiki's I've used are an absolute nightmare because you say "we're tracking issues in X, documenting in (wiki)Y and building in Z" and Y doesn't…
-
No, Jira doesn't do assign to groups. To change assignees, you'll need to write a service that can re-assign issues according to your rules.