Is there a way to hide subtask for specific group of users?

[Eva]

Let said we want client to access this internal project but we dont want them to see the subtask that we create for the developer, is there a way we can hide those subtask from the client?

Thanks in advance!

[Nic Brough -Adaptavist-]

Sounds like a job for issue-level security - http://confluence.atlassian.com/display/JIRA/Configuring+Issue+Level+Security

[Eva]

Not quite. I guess I should update the ticket with specific details. We want the client to view the ticket, just not the subtask. And the issue-level is base off issue type and subtask drives off security from the parent (main ticket). Unless I miss something?

[JamieA]

The sub-tasks just need to have a security level that means the client can't see them. The security level can be set programmatically, eg through a post-function on create, or explicitly.

[Markus Lepper]

Jamie, as far as I know the subtasks _always_ inherits the security level of its parent.

[Nic Brough -Adaptavist-]

Bother! Markus, you are spot on, I should have remembered that. The sub-tasks automatically take on the security level of the parent.

I don't know if the security level inheritance is down to data on the sub-task issue table, or if it's dynamic in code. If stored, it may be possible to write code to overwrite it (e.g. raise parent issues at "low" then have a listener that updates all the sub-tasks to "high")

I don't think it'll work too well though - data from sub-tasks rolls up, and there are functions for "stop close of parent if open sub-tasks", which may fail if sub-tasks are hidden!

[Eva]

@Marcus - that's what I was thinking before, but it's been awhile since I revisit this open issue. So there is no way to hide subtask unless we hide the ticket itself. Hmm...:T

Anyway, thanks for your inputs!

[Nic Brough -Adaptavist-]

Thinking about it, I don't think there's another way to do it - consider the situation where you set a high security level on the issue and lower on the subtasks - it makes little sense to hide the parent. Any mixed level scheme would actually be confusing, and probably very hard to code for

I'd use links to do it instead. Users create the main issue, then developers create (clone?) a more secured issue as a holder for the actual work, and anything they don't want the users to see.

[Markus Lepper]

Hi Eva,

just a small comment: You linked the wrong Mar(c|k)us

@Marcus leads to another user (Marcus-Holt)... I'm Markus-Lepper...

BR, Markus (with "K" ;-)

[JamieA]

Hrm, my bad. Perhaps then just use linked issues with a "Composes" type rather than subtasks.