[
https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-24112:
---------------------------------------------
When I configured the bot a while ago i deliberately did not give it any kind of access
beyond creating issues since then if it went errand it could at most only delete its own
issues.
I don't know what you are looking for to have assigned - but one of the
benefits/sideeffects of having it configured so those who are component owners get
notified about jiralint is that component owners will see issues. So not sure what is
trying to be solved with assigning to sepcific users - but if needed the minimum would to
grant the bot committer status - but then it can actually do "damage" so just be
aware of that.
I would recommend using a different bot for that though.
document pre-staging steps (including creation of N&N JIRAs) in
devstudio release guide
---------------------------------------------------------------------------------------
Key: JBIDE-24112
URL:
https://issues.jboss.org/browse/JBIDE-24112
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.4.AM2
Attachments: jiralint.user.no.perms.to.assign.txt
Need to document pre-staging steps (including creation of N&N JIRAs) in devstudio
release guide. Also can create a job in jenkins to wrap the creation of the N&N JIRAs
so heir creation is less error-prone.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)