search

Icinga / icingaweb2-module-jira

GNU General Public License v2.0
42 stars 16 forks source link

Provide project restrictions #12

Open Thomas-Gelf opened 5 years ago

Thomas-Gelf commented 5 years ago

'jira/projects` -> comma-separated list of allowed project names

MarcusCaepio commented 4 years ago

Hey @Thomas-Gelf , would it be possible, to set project permissions based on roles? E.g. Role A only see issues vom Project A, Role B from Project B and so on. Right now, I have the problem, that every role can see every issue from every project, where the jira "bot" account from the module configuration has access to. Some kind of filter, like in the monitoring module would be great.

slalomsk8er commented 6 months ago

I have a default project set but it isn't preselected in the issue creation form at /icingaweb2/jira/issues/create?host=example.com

image

This is quite bad, because the open dropdown will overwhelm the users with, currently, 38 projects to choose from and only one has the required fields for the integration to work.

slalomsk8er commented 1 month ago

It looks like the modules configuration UI is filling the wrong config name in /etc/icingaweb2/modules/jira/config.ini.

If I set 

[ui]
default_project = "ITSM"

New issues are correctly pre filled but the UI is setting

[ui]
project = "ITSM"

which does noting AFAIK.

Same for default_issuetype vs. issuetype.

Opened separate issue https://github.com/Icinga/icingaweb2-module-jira/issues/141 as this isn't related to permissions and would only provide a workaround by restricting the invalid choices.