JamieA Expert

I can't see it working with Robert's script. You're right, the page knows about it, but it's not being passed to your behaviours script.

Hrm... in your example you get the parentIssueId from the form, which is correct for getting the parent. But there is nothing available for getting the issue that the new issue will be linked to. I don't think Robert's example will work because the epic link is not created until the issue is submitted. Even so, I'd…

This is covered in-depth here: https://answers.atlassian.com/questions/110373

> Is it possible that this is a product of the migration from 5.0 to 6.0? I can't see how that would be possible... > before attempting the upgrade I would upgrade, but I don't believe that will fix it.It's complaining about getValue() on LazyLoadedOption, but that class does have that method. Not sure why it's saying…

Are you sure the condition is exactly like what you have put, and not one equals sign?

What type of field is Demo Required?

Yes, it should be that. The stack trace doesn't affect anything functionally, it should still work fine.

The stack trace is an outstanding issue that should be fixed in the next version. Your condition should be: cfValues["Message Source"]?.value == "EFDIS" Validator examples are…

That is doomed to fail. You can create a staging version of 3.1.2, do a space migration to the staging version, then upgrade the staging version to 4.3. Then if you have some other instance of 4.3 you can do a space migration to that. I recently did this for 50-odd spaces... all automated, and worked fine.

there was an issue with cloning the security level which was fixed, but not sure if the fix is in 3.1.3. Is that the reason you want the sourceIssue?

It's hard to respond when you add a similar comment to multiple question. What version of the plugin are you using?

I would use an issue security level scheme, and use a post-function to switch the issue between the various levels. I don't think this is a good use case for the behaviours plugin.

You can do it through hacking the workflow XML, but the easiest way is to use the graphical workflow designer. After drawing the transition you have the option to use a common transition, or clone an existing one. Would be good if this was available in the old-style UI, as I don't like doing things graphically.

I do not think you are wrong, per se. But I'd argue there are several cases where it's useful to have the content inline. For 1), screenshots, I can see a new comment and the supporting images and don't need to open jira. Conversely, by your argument a mail notif could just say "something's changed, click the link". 2)…

JIRA doesn't do this, vote for https://jira.atlassian.com/browse/JRA-6207 If you use script runner you can add a post-function that will send a mail that will include attachments: https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Sendacustomemail But you need to define the mail template,…

Just disable the plugin and see if anyone complains. If no one does you don't need it.

You don't need this anymore: def dirUser = ApplicationUsers.toDirectoryUser(u) as users have been normalised, and tfft. So just delete that line and use "u" instead of dirUser. That's what this is trying to tell you: Possible solutions: getPropertySet(com.atlassian.jira.user.ApplicationUser)

Use ComponentAccessor... there is information on the changes you will need here: https://scriptrunner.adaptavist.com/latest/jira/releases/release-4.1.4.html You will probably need to use the fully-qualified class name.

What you have should work - looks ok to me anyway... What version of jira, version of plugin?

The UI might time out, but the copy operation should complete in the end. If there are any errors, they will be in your log file, so can you check that?

6.3 has a configurable URL for gravatars. Since that release, I've dropped the rewrite rule method and just point to an app that can look up the picture from the mail md5 digest. This could be written as a jira plugin even. The other reason not to use rewrite rules anymore, is that 6.3 inlines the avatars if they are…

Hi, yes it is. But could also be done with urlrewrite.xml with vanilla jira.

IMHO there is a better alternative, which is to use url redirection to redirect requests for jira avatar images to whatever servlet etc you have that provides images given a user name. Example of apache rewrite rules: RewriteRule /jira/secure/useravatar\?size=small&userId=(.*)\& /picture/viewPhoto/$1?width=16&height=16…

I have not used the AppFusions one, but with my own Kerberos authenticator it worked fine from .net, assuming you have set: serviceProxy.Credentials = System.Net.CredentialCache.DefaultCredentials

Sorry, I'm not familiar with doing this without any code. It's possible that you just don't get textutils. Try putting this in your velocity to see what's available: #foreach($p in $ctx.keySet().toArray()) $p.toString() - $ctx.get($p).getClass().getName().toString()#end

Can we see the section of the atlassian-plugin.xml that defines the new panel?

Only if you are calling super.getVelocityParameters in your getVelocityParameters method... are you? You can also populate them with stuff like that by using: JiraVelocityUtils.getDefaultVelocityParams(authenticationContext)

You've already reported this as https://studio.plugins.atlassian.com/browse/JBHV-184 ... ? Reporting it in multiple places is not going to make me look at it any faster.

You should put a question on the plugin page. There are also other plugins that offer the same functionality, eg this is one of the built-in scripts in the script runner plugin.

I was asking if you were using the latest version of the plugin for your jira version...?