Radek Antoniuk

Hi @shrutiaggarwal3012, The selector selects the issues basing on the comments from the git changelog, so yes, it can take them from any branch you set the build for. For...

I like this approach for the decomposing and cleanup part :) @artkoshelev are you still up for it? @olamy for the backward compatibility, how about scheduling it for 4.x and...

I'm a believer of the approach that if we want the OSS projects to be alive,non-buggy and up2date with recent (here recent meaning

@artkoshelev what do you think about rebasing this to `feature/4.0` ?

@artkoshelev would it work to leave a `@Deprecated` `JiraSite.getReleaseNotesForFixVersion()` and call inside it `JiraCreateReleaseNotes.getReleaseNotesForFixVersion()`?

@artkoshelev what do you think about rebasing this to `feature/4.0` ?

Hi @mrvcmrvc, Very good analysis and as you pointed out, this was just not implemented fully in all the steps. Maybe that logic could be extracted and use across all...

I'll take a look at this tomorrow because it looks like some of the code is duplicated from the original `JiraIssueUpdateBuilder` class which as @oleg-nenashev pointed out should be usable...

@eskobaba what about https://github.com/jenkinsci/jira-plugin/pull/101#issuecomment-226165515? did you try this one?

@aatarasoff > I don't know how builder will look in pipeline, but I think that notation like: > > ``` > jiraIssueUpdate( > jqlSearch: jql, > workflowActionName: action, > comment:...