[
https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-23536 at 11/25/16 12:00 PM:
---------------------------------------------------------------
There's API to query default assignee based on a component
https://issues.jboss.org/rest/api/2/component/12317750 ->
https://docs.atlassian.com/jira/REST/6.4.9/#d2e4713 -> ...
but for issues which are automatically closed when the commits are added, there's
little need for this add-on. That said, N&N JIRAs *DO* need an owner/default assignee,
so there's value for those.
was (Author: nickboldt):
There's API to query default assignee based on a component
https://issues.jboss.org/rest/api/2/component/12317750 ->
https://docs.atlassian.com/jira/REST/6.4.9/#d2e4713 -> ...
but if the issue is automatically closed when the commits are added, there's little
need for this add-on.
components.py should store the assigned user
--------------------------------------------
Key: JBIDE-23536
URL:
https://issues.jboss.org/browse/JBIDE-23536
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.4.2.Final
Reporter: Jeff MAURY
Assignee: Nick Boldt
Labels: build, release, release-eng
Fix For: 4.4.3.AM1
The file components.py is used when created JIRAs during the release process. One JIRA is
created per component. But those JIRAs are not initially assigned to a user, so the user
of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file
stored as well the JIRA user id, then this could be done automatically
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)