Comments
-
You are going to need coding to do that, which pretty much means writing your own add-on, or buying one of the add-ons that lets you script fields.
-
Velocity has a #parse command, which lets you re-use other templates.
-
You've added the agents group(s) to the "can log in" settings under "global permissions". That means all new users get added to the group automatically. Check the permission, and chop it down to just the user groups you need automated additions for. Then go through your groups and remove people who have been added…
-
I've seen a lot of places use it for training and learning, but it tends to be used as part of a set of tools. It's great for content, but there's no tracking of learning or course completion - that tends to be done in other systems (often JIRA because of the tight integration possible between the two) I've not tried the…
-
Could you give us a bit more context? LMS = Least Mean Square to my mind (which it doesn't work for, because it's not a calculator), although realising you don't mean that lead me to Library Management System, Last Man Standing and so-on. Could you explain roughly what you're looking for here? The answer is "probably", but…
-
Apologies, I keep saying "derived", but the right word is "calculated" Start at https://confluence.atlassian.com/display/JIRA041/How+to+create+a+new+Custom+Field+Type#HowtocreateanewCustomFieldType-Lastcommentedusercalculatedfield (it's for Jira 4, but mostly still good for V5 and 6)
-
Ah, I see. No, you can't do this natively, and I don't know of any plugin that would do it either. There's also a potential problem with it - if you wrote a "derived field" that does it and puts the second query on-screen in the issue navigator, then you could take out your system. Think what would happen if you queried…
-
No, I'm afraid I still don't understand. I see that you have a search result in the issue navigator, but you want another search in it? The point of the issue navigator is that it returns the data for what you searched for. I don't understand the content of the column. The best I can get is that you want the column to have…
-
I'm really sorry, I do not understand the requirement? "issue.id should be filed the current issue.id from the issue it is shown in the issue navigator" is the bit I am stuck on. JQL searches for issues. When you have a list of issues, you can display the data for those issues. The issue navigator is one such display, and…
-
You add the field to the issue navigator, and it should appear. By default, just having a "view" template named in the atlassian-plugin.xml should allow you to do this (but you can override it, or even disable the usage in the navigator column). If it does not appear on the list of fields on offer when you try to add…
-
And modify code to enable functions to use it.
-
I'm not sure a "group by" is actually useful. Think of it this way - JQL is there to identify issues, not report on them. It therefore drags back a list, which is then pushed through some form of reporting. That reporting could be an issue navigator, a gadget, a chart, a greenhopper board etc etc etc. Some of them might…
-
He did not say status, he said category. It's clear he doesn't mean project category, so it must be workflow category.
-
The question said category, so I assumed he meant category.
-
You'll need to hack the core code of JIRA, those three categories are pretty much hard-coded into it.
-
I don't think you can do that - once a sprint is done, it's done. There should not be any reason to want to add more to it, other than faking your velocity. If something is left out of the sprint, then move it into the next one, comment that it's a mistake and move on.
-
I just read what I think Dieter just read too. Igor's answer is correct - Gri does not seem to have spotted the point in the last sentence about actually performing the transition.
-
You could get a post-function to run external code (scripts or programs) on the JIRA server if you wanted to - java has a simple "exec" call to run other stuff.To look at the checkbox, it's the same as any custom field usage in a post function - you can read it from the issue - the links to the developer documentation…
-
There's two parts to this. First, a checkbox is easy - go to admin -> custom fields, and add a "multi check box". Give it a single option. Then go to admin -> Screens and find the "issue create" screen you want to add this to. Add the new custom field. The second part is handled by the route you've started down - you need…
-
It's a low priority or edge case - most JIRA users simply don't need to change the type of a field, and we're mostly yelling for other features.
-
Create a new multi select field Run a search for each separate label, or group of labels Bulk edit each result set to add data to the new multiselect (I'd look at using the script runner to automate this as much as possible)
-
No, that will not work. The SQL is basically right idea, but you can only convert fields between custom field types that use the same storage methods for their data, and have compatible data. Select, multiselect, radiobutton and checkboxes are one set, short and long text another set. Multiselect and Label are NOT…
-
Er, no. Do not "restart jira". Stop it before you run the SQL. If you change the database while Jira is running, you could end up with a corrupted dataset because it caches things. Ideally, take a database backup first as well
-
There's a bit of a flaw in JIRA's implementation of the boards here. You can not drag an issue to another status in the same column. The boards only allow for a change of column. A couple of options: * Use the "impediment" flag instead. (Probably not ideal for you, but I had to mention it) * Add another column to the board…
-
Run the filter and then write some code that adds up the totals in whatever application is you've written the REST code into
-
Save the filter and look at it - most of the ways of viewing a filter will give you totals. Note that JQL is NOT SQL, and it doesn't have anything to say about the results it pulls back. All it does is give other parts ofthe system list of issues to work with.
-
Really, don't bother. The JIRA database is built for data storage, not reporting or querying. As an example, take a simple custom field - the SQL for answering "What components are on ABC-123" involves joining at least six tables together. Or for "what colour are the issues in that project? (colour being a custom field)" -…
-
JIRA has two "fields" (one of them isn't a field, but for this, it might as well be). The Status tells you where the issue is in the workflow. It does not tell you anything about the issue's resolution, even though it might say "resolved", "closed", "done", "fed to penguin", it's just an indicator of where it is.…
-
It's possible for an admin to deliberately disable it, that would be my first guess (I am assuming you can see Jira in a browser). If it's enabled, then it's probably a network thing.
-
For a correctly configured Jira, you should find it's https://jira.inside-company.net - you can see it from the "browse" line if nothing else. You can also do a really simple check - read an email from an issue comment or change - they build the urls you find in them from {baseurl}/{target}. If an email says…