Comments
-
Yes, it is, but you don't need arbitrary objects to do any of that. Just issues. Epics need to live in projects as they are issues, but that doesn't stop issues from other projects being added to them. For another layer of items like that, try Portfolio
-
JIRA is an issue tracker, not designed for random arbitrary items. It groups issues into projects, and then boards look at ranges of issues. Could you explain what you're actually looking to do here? What is the benefit of this X for the end user?
-
Log in as an admin and go to an admin screen, then look for "shared filters" under "system". While you're there, consider removing his shared dashboards too.
-
See https://confluence.atlassian.com/display/JIRA/Searching+for+Issues concentrate on the "reporter" field
-
>best to be a public facing site for clients being able to submit bug reports and track the procession? Is it Software or Service Desk edition of JIRA? Both. You need to work through what you really want and choose the most appropriate. If you want your users to see all the details, and be aware of what your developers are…
-
Yes, the permission schemes are designed for this. At the very basic level, they can do a simple "if in group X, allow action Y", but they're a lot more powerful. You can do things like "if in role X for this project, then allow Y", and then put groups into roles. See…
-
Same answer really.
-
Go to the project you want to investigate, and look for the admin settings. In there, look for the "issue type screen scheme" - this says "issue type X uses scheme Y". Now you have scheme Y, look at that in the Admin -> screen schemes page. You'll find the scheme maps the Create, Edit and View actions to individual…
-
The screens listed in Admin -> Screens could be used for anything (view, create, edit or transitions). You need to work out which one is in use for "view" by reading through the "screen scheme" configuration of the project, as Jobin said.
-
Yes. Code.Hack the core of jira or do something vile with javascript.
-
The answer here is "code". The view screen pulls certain fields out of your list into panels to group them logically- fields with users, fields with dates and all the built-in system fields. The rest are place in the custom field area. To move other fields out of the custom field area into arbitrary places, you need to…
-
Does that mean you've written a plugin, or just added a standard custom field?
-
Two parts here: Sorry, you've misunderstood. The create, edit and view screens are determined by the screen-scheme and issue-type-screen-scheme. They're pointers to the screens to be used. This is so you can do "for issue type A in project B, use screen C to view and edit, and screen D to create it". You've got the three…
-
It's perfectly possible, it turns out the problem here was simply that the poster didn't quite grasp that they needed to change the VIEW screen at first, and then, that fields will only appear when they have data.
-
Yup, that's why I'm asking - as the answer is there in the link in the question, I'm really not sure why he's asking the question! And, on the back of that, I often misunderstand questions, so wanted to check. (Also, that's why I'm waving at the documentation - if I've understood the initial question correctly, then the…
-
That's the "issue view" screen. You add the custom fields to the "view" screen in the "screen scheme", and they will appear on the issue details. There's a link to the documentation in the question you've linked to. (I really do think I'm completely missing the point of the question here though)
-
Doesn't matter - OS X runs other files in there.
-
Done it on a MacBook Air, it's virtually the same as following the Linux guide (as long as you understand where to look in the MacOS file tree - stuff is a little different to a Linux file tree. It's still similar enough to recognise though, and once you know that /foo/bar in linux can be found under…
-
No. A user must be able to see an issue to get any emails related to it. You can go around this with plugins, but it is a potential security breach if you do.
-
It must be a user picker, not a select list or other type of field.
-
You can configure standard user-picker fields to follow similar rules as the assignee field does. Create one and have a look at the configuration after its been created - you should find a way to set up some rules. See…
-
Your structure is nonsense. A column in agile, by definition is a distinct status (or set of status) in the lifecyle of an issue. If you put the same stutus in more than one column, your board is intrinsically useless because it's now telling you absolutely nothing. However, Agile columns can be thought of as a form of…
-
It's hard work with javascript, and even harder to get right. Behaviours does make it a lot easier
-
Hacky javascript, or use the Behaviours functions built into the Script Runner add-on (also javascript, but using the add-on means you don't have to maintain the js yourself)
-
You can put it on screens and see it, but it's not actually a real data field, so you can't edit it. It's not really data, it's simply saying "when was the issue last resolved, according to the history" and displaying that. To "edit" that, you actually need to put different timestamps on your history, which would…
-
Not without coding. The form really is just a way to get JIRA to send a general "help me obi-wan-jira-admins" email, adding fields to it does not do a lot because the data in those fields is not going to do anything other than be added to the email.
-
That sounds like your index might be broken. You can test this - find an issue that has a resolution when you look at it in the issue view, but is not showing as struck-out. Edit it, making some minor change (add a full-stop in the summary or description or something similarly low-impact). I expect you'll find it's now…
-
There should be a "log work" option on the actions menu. If it's missing, then you probably need to check the permission scheme for the project and make sure you have the "log work" permission.
-
Just those who are in the "can use JIRA" group(s)
-
You need add-ons to update custom fields. For Cloud, try enabling the "misc workflow extensions" add-on (it's pre-installed and free) - that adds "set field value from string/regex" as a post-function.