Allow users to update other fields during transition. (#84)

Author: jpavlav

CHANGES.md

@@ -1,11 +1,11 @@
 # Change Log
 
-## 3.1.0
+## 3.2.0
 - Add new feature to ``jira.get_issue`` to allow for stripping of Jinja templating artifacts from resulting output. (Removes instances of {{ }} from results.)
 
-  Example: You pull a jira with ``code`` block in a comment or the description. To the API that shows up as {{ code }} which is jinja Templating and will cause 
+  Example: You pull a jira with ``code`` block in a comment or the description. To the API that shows up as {{ code }} which is jinja Templating and will cause
   issues when trying to use that output anywhere else in a workflow as it cannot find the `code` variable in the context.
-  
+
 
 ## 3.0.1
 

actions/transition_issue.py

@@ -1,12 +1,9 @@
 from lib.base import BaseJiraAction
 
-__all__ = [
-    'TransitionJiraIssueAction'
-]
+__all__ = ["TransitionJiraIssueAction"]
 
 
 class TransitionJiraIssueAction(BaseJiraAction):
-
-    def run(self, issue_key, transition):
-        result = self._client.transition_issue(issue_key, transition)
+    def run(self, issue_key, transition, fields):
+        result = self._client.transition_issue(issue_key, transition, fields=fields)
         return result

actions/transition_issue.yaml

@@ -13,3 +13,9 @@ parameters:
     type: string
     description: ID of transition (e.g. 11, 21, etc).
     required: true
+  fields:
+    type: object
+    description: >-
+      Fields to update on the issue. For example to set resolution to "Fixed"
+      {"resolution": {"name": "Fixed"}}.
+    required: false

pack.yaml

@@ -6,7 +6,7 @@ keywords:
   - issues
   - ticket management
   - project management
-version: 3.1.0
+version: 3.2.0
 python_versions:
   - "3"
 author: StackStorm, Inc.