JamieA Expert

How does it prevent issue A from being closed? This is some additional condition you've added...?

If it doesn't work then that version, which is very old, doesn't support selective copying of attachments. Setting the initial status is also not straightforward, I would try putting a fast-track function on the create step, and checking for the presence of something the Clone function can set.

Not really ;-) Presumably you were testing on a dev instance so you didn't take down your production jira...

You create an issue. The post-function creates another issue and links it. The issue that's created also has it's post-functions invoked. Therefore you get a never-ending chain of issues. If you want to create another issue that has the exact same workflow, and you want an issue cloned on the create step, you need to put…

There is a full example of what Dieter is talking about here: http://confluence.atlassian.com/display/DOC/How+to+Force+Links+to+Open+in+a+New+Window It can be done just by stuffing that stuff in the custom html, as well as a speakeasy extension, or using {html} macros, if that is enabled on the hosted confluence.

Maybe they were resolved then reopened? Or you have a resolution value called "Unresolved"?

Great, can you mark my answer as correct, by clicking the check mark ;-)

It's: resolutiondate >=-1w Tip: You could run the "Recently Resolved" filter from any project, switch to advanced, and see the jql for this like that.

You need to add a condition to the transition - if you mean "jira administrator" permission then you could add the "user is in group" condition with a value of jira-administrators, if you mean project admin, then you could use the User Permission condition.

Thanks Rick... I really didn't want to break compatibility but had no choice. Thanks for that comment anyway.

Hi Rick. Fair enough. I did fix the performance issues with those two, either last release or next release.

You can't atm... that functionality was removed when the GUI was removed. Maybe I can put that functionality back. What do you want to disable?

Sounds like a bug, please could you create an issue at https://jamieechlin.atlassian.net/browse/GRV

Script runner plugin has a jql function where you can search for issues with attachments with a particular name or extension, issueFunction in hasAttachments ("pdf"<a>)</a>.

It's part of the Resolve Issues permission... look in your permission scheme.

What do you actually mean by "and if found, link to that issue instead of creating a new issue"? You mean create the issue and link, or not create the issue, and link what?

You are going to have trouble bailing out of the "create" process from a post-function. Maybe try doing it in a validator...? There is some code for the behaviours plugin here: http://blogs.onresolve.com/2010/03/audo-duplicate-search-in-jira/- but you could get what you want out of it. Or use Boris' example.

Set up your maven proxy: https://answers.atlassian.com/questions/20079/plugin-sdk-does-not-use-http-proxy

No plugin that I know of I'm afraid...

I have done exactly this before, but code not available. Are you looking to know if it's possible (it is) or to get the code, or just for some API pointers?

Thanks for that explanation, that's very clear. That you can't use expression with script fields is: https://jamieechlin.atlassian.net/browse/GRV-695, and I hope to focus on JQL functions within the next 6 weeks.https://jamieechlin.atlassian.net/browse/GRV-713 for the DST issue.

Just to help me understand, is this massively significant? Are you querying on durations that are so short they are affected by a lost or gained hour? I don't see a solution to this from the JQL side other than the code taking into account DST. But this should be solvable with a script field? You seem to be saying that is…

Would be helpful to know how it's not working... did you check the logs? It's probably the positioning of the function within the other functions - the way you have written it this function needs to be first, or at least before the ones that store and reindex the issue.

You could edit the velocity template for this, eg: <classes>\templates\plugins\jira\projectpanels\roadmap-panel.vm However this would then apply to all versions across all projects. You would remove the $textutils.htmlEncode(...) surrounding $version.description. I'm not sure I'd bother though, in 4.4 entering a…

It's a bit of a pain, but using the SDK it should not be much more than changing the version number in the pom, and running atlas-run. And waiting while an area of internet the size of Ireland gets downloaded.

ok, i'll take a look

That's totally fair enough. But, if you want to ensure support you can either pay, or be prepared to do the work yourself. Also I don't / can't attempt to reproduce any problems found in any version other than the most recent. If you have a simple use case then just use javascript...

yeah... there are always going to be bugs in the javascript side because of the nature of things... manipulating the dom is not a "supported api" so can change between minor versions. I have a big plan that I want to use behaviours for so it might get some love within the next month or two.

I never gave any official guarantee of support for any of my plugins, they're all marked as unsupported. Yes, it's still active, the plugin is still in use by me therefore will keep getting updated. If I haven't replied to a bug report you raised it's just because it's not my focus at the moment. It will become my focus in…

Remove the cf validation for the time being and check the linking works. What you have looks correct but for clarity use: def issueLinkManager = ComponentAccessor.getIssueLinkManager()issueLinkManager.getOutwardLinks(issue.getId()).any { it.issueLinkType.name == 'Implementation'} If that doesn't work can you post a…