Can anyone advise if and how I can hide the Member Groups folder within Members in Umbraco 8 for a specific user group?
Failing that, can I give users access to the members section but prevent member group deletion?
thanks
From an API point of view this can be done now with events so it would be up to you at a granular level to decide what rules are applied to hide properties. You can subscribe to the event EditorModelEventManager.SendingContentModel and modify the outgoing model which means you can add/remove tabs/properties, and pretty much whatever you want. If you wanted to pursue that without modifying the core It would also be possible to create a package to have some UI to control these rules if you wanted.
Related
I'm trying to work out the best way to have content owned by members (one member has many properties). I tried using relationships but these don't seems fully featured yet and I've also used a member picker on the property which works fine.
What I'm missing is being able to see all owned properties for each member from the members tab (along with the ability to edit/view) from the back office.
Is there a way to do this using the member picker field or do I need to use relationships?
Thanks
I think you can use the EditorModel events to do this. You can use these events to interfere which data will be send to the backend. If you want to e.g. hide tabs, this an easy way to do so.
You can read more about this in the documentation about EditorModel Events.
Or if you do not want to do everything yourselves, check out the Plumber package. It might not do exactly what you want, but it will bring you very far i guess.
I was asked to separate access to a particular Jira project by component. e.g. user "a" can see issues created for component "a", but not component "b". conversely, user "b" can see issues created for component "b", but not component "a".
I know that I can limit access to a particular project to one or more users, but I was unaware of a way to filter access to one or more users by component within a Jira project.
Is there any way to limit access to one or more people to a subset (less than all components) of a project?
I did a search for a Jira plugin that might offer this functionality, but did not find what I was looking for.
N/A
N/A
I don't know if that's possible by using a component (I don't think so), but there is an alternative approach which might be sufficient as well:
You can adjust the Browse Projects permission like this:
You can grant permission to a group custom field value. Then you could choose a custom group field (create one if not available) which will be evaluated on each issue. Then, if you create an issue and add a group to this custom field in that issue, only users from that group have access to view the issue. Take care that you remove the any logged in user setting for "Browse Projects", otherwise the group custom field does not have any effect. There is also a KB article here in Jira's documentation.
The first question is what are you trying to do? Why do you want to restrict who can view issues?
Jira has Issue Security Schemes that can do this based on setting the security level according to the component, or other fields. I'd use a custom create post function
But what happens when the component is changed? Now you have to restrict editing too.
Is there is a possibility in TFS 2013 where a particular work item like Bug an d Change Request has to be created and closed by Testing team and task by developers.
No, we cannot achieve that as the requirements conflict each other.
You can set the permission Edit work items in this node for a
specific user group on an specific Area. But it applies to all the
work item types.
You can customize work tracking experience for restricting access to
work items:
For example, you can prevent the majority of project contributors
from creating the work items by adding WITs to the Hidden Categories
group. You can create a hyperlink to a template that opens
the work item form and share that link with those team members who
you do want to create them. But you cannot prevent other team members
closing the work items.
You can restrict access to work tracking objects in one of two ways:
By adding WITs to the Hidden Categories group, you can prevent the majority of project contributors from creating them. You can create a hyperlink to a template that opens the work item form and share that link with those team members who you do want to create them.
Set a condition field rule, a condition-based field rule or a combination of the two that applies to a group. You can restrict changes from being made to a field by specifying a qualifying rule and making it apply for a specific group.
Conditional rules can include CANNOTLOSEVALUE, EMPTY,
FROZEN, NOTSAMEAS, READONLY, and REQUIRED elements.
For more information about how to customize WITs, see Modify or add a
custom work item type (WIT).
We're about to implement TFS 2012 and I've been having some fun customizing some work items to aid us in our reporting. One issue we have is our reporting based on clients.
Our Product Backlog Items keep our requirements, however, we need to report our requirements per client (government regulations). Some requirements will affect all clients, some will only reflect certain ones. I've been able to add a global list of clients along with a multi-select option and that part is working great.
The issue is we need to also note the requirement number for each selected client. I know I can go in and add a field for each 'Client Requirement', but as that list gets bigger, that screen will be insanely huge.
Does anybody know of such a way to implement something of the sort?
One option would be to create a custom Work Item Type for Clients. Then link your PBI's to the appropriate client WI's. When you create a link you can enter a link comment also which you could use to capture the client-specific requirement number.
I would create a custom "Client Requirement" work item that has the list of clients to select and includes a field for Client ID. You can then either use the related link type or create your own, maybe "Implements \ Implemented By" so that you can create a Reporting Services report that pulls the ID's
Is there a way to hide specific TFS work item types for some user groups? E.g. Client should not see Bugs.
Is there a way to hide specific WI fields. E.g. Client should not see Estimation field.
The only way that I know so far is using the security rights on the WI area field.
That allows you to create specific areas, remove read rights for some users/groups and than all WI in that area will not be visible. The problem is this ads new responsibility to the area field that leads to duplicate tree structure.
I am aiming for more flexibility, maybe something at field level.
I really can't understand how this is still not available.
Thanks in advance.
This is level of security granularity is not available these days.
What you can do is make an integration with another system like sharepoint where you expose the fields you want. You can use the TFS Integration Platform for this .