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; } } }

Member permissions on Jira ticket specific field

Arthur Harutyunyan

Hi Admins,

I have 2 types of projects, lets call them INTERNAL and EXTERNAL.

INTERNAL: This is a project where the internal team is communicating over the tasks and organizing the whole SDLC

EXTERNAL: This is a project where the business level discussions are stored and the cost of the task/project is stored in a special field, lets name this "Cost"

PROBLEM: Sometimes there is a need for an INTERNAL member(a developer or someone else) to participate in the discussion in EXTERNAL one. So, the idea is to have the "Cost" field hidden from that internal member, but he should be able to see the other fields.

Hows that possible? Any workarounds?

Thanks,

Arthur

Accepted answers

Nic Brough -Adaptavist-

Hi Arthur,

It looks like you got an answer was written by an AI that did not really understand the question, or how Jira works.

Jira does not have field security. It only does issue security. Either you can see an issue and all of its fields, or you see nothing.

There is no way to obscure your "cost" field alone.

There are a couple of apps that do provide "secured fields" though, they may be worth look. (Unusually for me, I'm not going to plug any Adaptavist stuff - even the most powerful one we have won't do it totally securely - Behaviours can hide fields in the browser, but the content is still delivered in the raw HTML)

All comments

Valerie Knapp_dpp5c6

Hi @Arthur Harutyunyan , thanks for your question.

It sounds like this could be a good use case for an Issue Security Scheme - Configure issue security schemes | Atlassian Support,

How you could apply this, you can create an issue security scheme in your instance and apply it to the project which should be used only by a smaller group of users, let's say.

Within that same project, you can have different levels of security to render the Jira issues more or less visible. You can also configure the security levels in such a way that someone doesn't see the issues unless they are specifically associated with the issue. So, someone wouldn't see the issue until they become the assignee / when their input is requested.

Please check out the documentation and give us your feedback if you think this would be a viable solution for you.

Cheers

Arthur Harutyunyan

hi @Valerie Knapp thanks for quick answer and thanks for your help.

I will dig into it and back with my feedback.

Regards

Nic Brough -Adaptavist-

Hi Arthur,

It looks like you got an answer was written by an AI that did not really understand the question, or how Jira works.

Jira does not have field security. It only does issue security. Either you can see an issue and all of its fields, or you see nothing.

There is no way to obscure your "cost" field alone.

Arthur Harutyunyan

hi @Nic Brough -Adaptavist- thanks for your feedback.

To be honest this seems to be a very trivial case and I was pretty sure that Jira could handle such cases

Anyway, I think lot of people face this kind of requirement during their Jira administration. So, it worths to have this feature as well. Please share your opinion on this point.

"There are a couple of apps that do provide "secured fields" though, they may be worth look."

Can you please share some of apps you know so that I can give a try ?

Thanks,

Arthur

Nic Brough -Adaptavist-

I'm afraid it's not trivial case, it's actually very hard to implement, and easy to make it non-performant.

The first two apps at https://marketplace.atlassian.com/search?query=field%20security have done a good job of it though.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud