Added possibility to filter JIRA request also by additional fields #97
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d customfields. Instead of using the issues API, it will use a jql search instead.
|
Does not compile. @slowflyer74 ping me when it works. |
|
It's compiling now, but there are Test failures. Not sure if they suceeded all before? |
|
They did. You can generate the approvals tests by removing them |
tomasbjerre
force-pushed
the
master
branch
6 times, most recently
from
b65386f to
4b5ca4f
Compare
tomasbjerre
force-pushed
the
master
branch
2 times, most recently
from
1dcafd8 to
9cb1ff1
Compare
tomasbjerre
force-pushed
the
master
branch
3 times, most recently
from
a1bf908 to
ccace50
Compare
tomasbjerre
force-pushed
the
master
branch
7 times, most recently
from
5955bcb to
7dc00e2
Compare
tomasbjerre
force-pushed
the
master
branch
2 times, most recently
from
0d44d86 to
0ab5a28
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…and customfields. Instead of using the issues API, it will use a jql search instead.
This feature is needed, if you develop for e.g. multiple clients in one branch and in one Jira project, but each client should only see the commits that belong to him. So you can define a custom field and integrate this into the plugin configuration and filter out all other tickets that are of no interest.
Instead of using the issues api, this will use the Jira search api and create an jql query