-
Suggestion
-
Resolution: Duplicate
-
None
We are planing to invite our customers to post feature requests and defects about our software.
Right now, i can add only one field layout scheme to a project and all users will see all fields of this scheme. It makes no sense, e.g. that the customer can set a fix version, he should not be able to do so, as he does not know.
I would suggest a general solution, to avoid the discussion for every field.
1. Solution: A issue field security level (smiliar to issue security level)- For each field a security level is applicable. Only those fields are visible for the user group, that are a member of this issue field security level. Users/ user groups not a member of this security level will not see this field (the field is hid)
2. minor Solution: More detailed permissions for the system fields: e.g. "Set fixed version", "set component": not having the permission will not allow me to edit the fields (as is already implemented for assigning users)
3. Solution: create a master layout scheme for the project.
create a sub layout scheme on user group level. each user will see only the fields of their user group, even though all fields exit in the database. Some user groups may then see more fields than others.
In order not to generate errors with required fields, it should
be possible to set default values for all system fields (not just custom fields): e.g. default value for component=unknown, fix version=unkown.
maybe this issue could be solved by the requirement of adding a general customer object.
- duplicates
-
- Closed
- incorporates
-
- Gathering Interest
- is duplicated by
-
JRASERVER-5355
How to hide a custom field from a group of users
-
- Closed
-
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
-
- Gathering Interest
- relates to
-
- Closed
-
- Gathering Interest
[JRASERVER-3417] Hiding issue fields for some users /user groups
How is this solved/closed now? Because I still don't find any official solution for the required feature (hide fields for certain user groups).
Update:
Nevermind, I found a clear (and indeed disappointing) statement in https://jira.atlassian.com/browse/JRA-1330.
guys, if anyone is still looking for a solution: we described a pretty low level (i.e. soft-hiding, on the client side) approach to this issue here. Please feel free to look onto this and come back at me in any case of questions.
Disclaimer: this solution requers a small plugin of which we are the developers. Better be honest upfront 
You may want to watch the live fields features of JJupin that among others enables you to hide fields depending on any logic (custom field value, status, complex algorithms, etc). See examples on Supported fields page or Recipe on hiding Time tracking Information.
Henk,
This is almost a direct duplicate of JRA-1330 and if we can't do JRA-1330, we won't be able to do this. We will look at re-opening smaller issues that were incorporated into JRA-1330, but we wont reopen an all encompassing duplicate.
Cheers,
Nick
Henk Binnendijk
added a comment - Can this issue please be reopened again??? see the last comment of Scott Farquhar [Atlassian] and see call JRA-1330
Henk Binnendijk
added a comment - Can this issue please be reopened again??? see the last comment of Scott Farquhar [Atlassian] and see call JRA-1330 Guys,
We have two issues that are for the same thing - JRA-3417 and JRA-1330. I'm closing JRA-3417 for the following reasons:
I'll add everyone from JRA-3417 to be a watcher on JRA-1330.
This is the reply I gave via email to Steven, who contacted me personally:
Unfortunately this issue is not likely to be implemented this year.
This is because we are working on other areas that are both causes of
complaint (editable worklog, editing workflows), core components
(improving issue searching, sorting, notifications), and architecture
improvements (improving plugins, the build system).
There is also a lot of architecture improvements that we want to do under
the hood, and in the administration UI before we add this feature,
otherwise it will be too complicated for our users to use effectively and
easily (as I fear we have done with screen schemes / workflows).
I'm sorry that your feature isn't at the top of the list, but we do try
to listen to everyone, and we do implement the most voted for features,
but in this case we have to do other features first.
Please vote / comment on the issue, it keeps it at the forefront of our
minds, and we do use this feedback when implementing features.
Hi guys,
Unfortunately, this issue is still not scoped for a specific release yet. Though it is one of our top priorites issues and do hope to get it resolved sooner rather than later. We try to very open and transparent with our processes and have posted our selection criteria for new features.
We will post a comment when this issue is scoped.
Sorry for the inconvienience.
Cheers,
Nick
sebastian23 Also see my previous comment about "hiding" and using the CUTE for JIRA Plugin.