nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Subtask level security

Rahul Krishna

I know there is topic already on this, but is there a way to achieve this, we need to hide the information in one of the subtasks under a issue to general users and make it visible only for select personnel. Since subtasks inherit issue security from parent, we can either show all the subtasks or none at all.

is there any workaround for this other than linking another issue(already tried that) or a third party app?

Accepted answers

Nic Brough -Adaptavist-

Yes, and no.

Yes, because you can set security levels on sub-tasks via the REST API (you can't do this in the UI), rather than letting them inherit their security from their parent issue.

But, no, because it is not supported, gets changed unexpectedly (it gets blanked out on some changes of either child or parent) and is not consistently reported either. If, for example, you log 4 hours work on a "hacked" subtask, it rolls up to the parent issue for people who can see the subtask, but not those who can not. But if anyone reports on Σtime, if they can see the parent, it includes the sub-task that they can't see.

So, I tend to describe the REST trick as a "hack" or "bodge" rather than a "workaround" - it's got too many flaws to be useful.

I think you would be better off creating separate issues to be secured, rather than sub-tasks.

All comments

Nic Brough -Adaptavist-

Yes, and no.

Yes, because you can set security levels on sub-tasks via the REST API (you can't do this in the UI), rather than letting them inherit their security from their parent issue.

So, I tend to describe the REST trick as a "hack" or "bodge" rather than a "workaround" - it's got too many flaws to be useful.

I think you would be better off creating separate issues to be secured, rather than sub-tasks.

Rahul Krishna

Thanks Nic,

I created another issue called B and applied issue security and linked it to A(with subtasks). It works but from our perspective this A and B are templates and we clone these templates(used for onboarding different resources), when cloning there is an option to check clone sub-tasks and clone-links, when i check them both its only cloning A issue with subtasks but its not cloning issue B rather the new cloned issue is pointing just to old link B.

So we decided to clone A(with subtasks) and Clone B and link them together after cloning. You can see after a while its going to be confusing for the user.

I also remove clone prefixes and cloners issue link. just FYI

Nic Brough -Adaptavist-

Yes, when you clone B, you won't get A's subtasks cloned, because they're not part of B.

Rahul Krishna

thats not what i meant, two issues forget about the subtasks

A and B, link them together and if you clone A and choose option clone links

The result should have new clone of A link to new clone of B right, but thats not happening

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

permission

issue-type

sub-task

security