-
Notifications
You must be signed in to change notification settings - Fork 123
Feature/jira transitionbyname #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Feature/jira transitionbyname #57
Conversation
Here 2 PRs are mixed into one:
|
I put it on top of my changes for jira-deleteIssue as i gave the other one to merge yesterday, if somebody really want to merge it i can prepare branch with only transitionbystepname function i would have few more updates probably soon, and would be hard to remember which functions are working with others. |
This library seems to be most promising JIRA REST API client on PHP I've seen, but I'm not sure if it's maintained, because last commit was 1 year ago and there are lots of unmerged PRs. Library creator however is still doing something on GitHub according to his feed. |
I'm using it for few days - so don't know - it is very basic one but very easy to add your own functions. |
From architecture viewpoint there are some even more promising libraries, but they have 1 or 2 functions implemented, so I've chosen this library. |
PR looks good to me. Splitting would be nice, also added some inline comments around spelling / indentation etc. Not sure if author is up for fixing these things else we could merge it anyways. |
@jpastoor please add comments on PR's diff, rather then on commits in it because comments on commits are lost when squashing happens. |
The #57 (comment) isn't addressed as it seems. |
@@ -253,6 +271,8 @@ public function getTransitions($issueKey, $params) | |||
return $this->api(self::REQUEST_GET, sprintf("/rest/api/2/issue/%s/transitions", $issueKey), $params); | |||
} | |||
|
|||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove extra line, because methods should separated by 1 line, not 2.
StepName isn't a jira term, but it's easy to use step name (the name of the button above issue) to navigate. It's just easier to reffer it as text than as ID - even if text could be changed and ID cannot. but it would be more understandable if you would do: |
If you find it better (less going back and forward) I'm happy for you or anyone to make it properly :) |
Please rebase and solve conflicts. |
No description provided.