JamieA Expert

Maybe you could script the creation of custom field contexts. I don't know of any other way, short of hacking LabelCFType and its friends.

I thought that you could create a separate context for it, per project, then the suggestions will only be from that project. That was my understanding anyway, could well be wrong. Try it...

It's not, see https://jira.atlassian.com/browse/JRA-5865 for a discussion on that.

You need linkedIssuesOf . Once you have the first query working you can use that as input into the second. You will also need to OR it with the first query, so you get both the issues and their linked issues. You will end up with a big ugly query but by saving intermediate filters and using linkedIssueOf("filter = foo")…

I don't think you're going to get a correct answer based on the information in your question. But, if you install the java melody plugin, it will show you all the database connections, along with stacktraces from what created the connection. Using this, you can find out which plugin (it probably is a plugin) is creating…

As Chris said. AFAIK it will work fine. Official support will come in time.

It can be configured as a listener, in which case it would fire for the attach files option... Not quite sure what event it would be, probably "issue updated".

You'd have to change the code... you could use this function from the script runner plugin, or just extract the code from it.

I'm a fan of JCLI but isn't it easier to just use the built-in CSV importer? Google for the docs...

CQ is so broken today, |I give up trying to get the formatting right.

This was also created as a support request so I will add my answer also: You probably want a condition rather than a validator. Add the condition to the Approve transition only of issue type C. You can use a "Simple Scripted Condition" with the following code: {code} def parent = issue.parentObject def otherSubtasks =…

Double check you are using the SMTP address of the DL. I don't see why this wouldn't work. Maybe ask your exchange admins if it's being blocked, or if the user doesn't have permission to send to that DL.

And btw you're lucky, it takes around 90 seconds for that dialog to popup after the caches have been cleared on my instance...

* Get atlassian to implement com.atlassian.jira.issue.fields.layout.field.AbstractFieldLayoutManager#loadFieldLayout in a more efficient manner * Reduce the number of field configs * Reduce number of projects/role - probably too difficult * Try to find people who call: com.atlassian.jira.issue.fields.FieldManager#refresh.…

It's extremely slow after a cache clear event. My profiling show it's proportional to the number of field configs * number of fields, and also number of projects * number of roles, as there will be a db query for (N projects * M roles). After you have loaded the dialog once, it should then be much faster . Is it?

Seems this only works for inactive, not draft workflows. With drafts you can only change the description. This is annoying because there appears to be a bug in the viewworkflows project admin page, where the diagram fails (broken image) if the workflow has leading or trailing spaces.

There is a module in the JIRA Importers plugin that is disabled by default - I would look at the code for that, or even call it directly (more info: https://confluence.atlassian.com/pages/viewpage.action?pageId=293830712) Normally I would try to write some code given your effusiveness ;-) but I don't have the time right…

> but I though webhooks required websites at both ends Well, yeah, it does. But you can write a web server in a few lines of perl or python, even if all it does is write the json packet to a file system and call some more scripts. I strongly recommend avoiding creating your own format... yours won't handle nicely things…

Also note that this is pretty much what WebHooks are for - and all that code is already written.

OK... but the map you are creating is not very good for an interchange format. You should use something easy to parse... jira can create both JSON and XML representations of an issue, including all comments, history etc, not just fields. You should reuse that... then you can just stick your bit of JSON on the message bus…

I'd say why do you want to do this? Having said that, what you're doing doesn't seem too outlandish. You don't have to use the GenericValue but then you do need to list out all the fields, and then maybe use the issue.@property notation, if you want to iterate over a list of issue fields.

I think you will need to inject some javascript, then depending on JIRA.Issue.getIssueKey()you would do:AJS.$("#assign-to-me").hide()

The following should work: if (getActionName() != "Create Issue") { def assigneeChanged = underlyingIssue.getAssigneeId() != getFieldById("assignee").value getFieldById("comment").setRequired(assigneeChanged)} That should be applied to the Assignee field. It's not going to work though if the user clicks the "Assign to me"…

Also see the JQL functions in the script runner plugin.

thanks

Not currently. I thought there was an issue for this at https://jamieechlin.atlassian.net/browse/GRV but can't find one. If you comfortable programming you can send an email using a custom post-function, or call the SendCustomEmail function with the correct inputs.

kill -9? Depends on OS.

I'd leave it for another 20 minutes. The %age progression is not linear, the first 20% is for xml parsing, then 80% for import and indexing issues, 5% for indexing filters and so on, last 10% for restarting internally. Very approximately. If after another 20 minutes it's still dead, try killing it. If it comes up ok and…

new Date(lastLoginTimeStamp) will give you a human date, as it will be implicity toString'd. You might want to use a DateFormat depending on your meaning of "human readable".

[10030:"Lemons", 10031:"Oranges"] need to be valid options (IDs and names) for the select list. All that setFieldOptions can do is effectively remove options, not add ones that don't exist. > Just another question, where can I find documentation about com.onresolve.jira.groovy.user.??? like Formfield The important stuff is…