I have end users going in as stakeholders and adding new work items. we have a long list of areas and iterations.
I have created a custom group and denied them access to all areas and iterataions except the one they need but when they go create workitem, they can still see all the areas and iterations.
Yes, they cannot save workitem under an area/iteration that they don't have access to but is there a way to display only those areas and iterations that they have access to?
There is no such work item rule by default to hide Area and Iteration Names, you would need to customize your own work item control. The source below can help you start how to customize a work item control:
https://witcustomcontrols.codeplex.com/
Related
I'm trying to lock/deny the option to open a new work item with specific iterations.
I tried to do it with a custom field with same value of iteration id and
<PROHIBITEDVALUES> rule.
Then I understood that its not possible because iteration-id field load only after I press the "save" button and its too late.
There any other ideas how to do it?
There is not any build-in option to hide older/specific iterations in the Work Item field.
However, you can set the security for "Edit work items in this node" to deny and they will not be able to save work items with the area or iteration selected.
Besides you could also hide the iteration node(s):
Open Project settings>Project configuration
Select the Iteration Tab
Select the iteration that you want to hide
Click on Security > Add a "Deny View" permissions for the users that
you want to hide the nodes from.
The user will not able to see the iteration in the sprint.
update:
I need a command which calls a screen in a specific priority.
In detail:
I'd like to offer a menu entry to our users were they can simple change the work day calendar in employee data sets and nothing else. I know the correct way would be creating a lower prio screen and grand the user such prio for accessing employees. But these users are allowed to change more than the work day calendar! I just like to reduce the fields in screen for a more simple recording and maintaining of absence from work.
So they should be able to view and change the normal employee screen but with a special command (from command view) the should open the same employee but with reduced number of field. Simple: separated screens for different use cases.
I believe I have to solve it by providing a service program in infosystem or similar but I'd like to ask you for a better way of solution before.
In this case you can work with different screen context modes.
Please keep in mind, that screen modes works just within new screen descriptions.
(almost) Every element in the screen editor has an option called visibility scope (Sichbarkeit -> Geltungsbereich)
For example you could define a scope called EXTENDEDPERMISSION.
Then the element would be only visible, when you set the screencontext in FO to "EXTENDEDPERMISION"
..: set one screen context
.formula P|maskkontextfop = "EXTENDEDPERMISION"
..
..: set some screen contexts
.formula P|maskkontextfop = "VIEW1 VIEW2 LIGHTVIEW"
You can set the screen context in every event you'd like to.
For more infos you can search for "maskkontextfop" in the online help.
But keep in mind, that the user still can access all variables over the dynamic selection as long as you grant them the permission to these fields!
So if you really want, that a user (under no circumstances) gains access to some fields, you'll have to configure the right permissions.
We have a few bugs and change requests which have a complicated iteration path. This results in people coming over the team to ask 'Where do we raise items' a lot.
As you can't set a default value for the iteration path in TFS 2010 we think the best solution would be to add a string of text under the field which we can manually update every 7 weeks with the correct area to raise items in.
However TFS doesn't seem to allow just a line of text on its work items as a control. Is there a way to add a line of display text i.e. Not a field you edit, but just to inform those writing the items?
Please note that it needs to be visible at all times, using the tooltip 'help text' field on a control is not enough in this case.
You can use the LabelControl for this purpose.
You can not have a default in the work item for the iteration path, but what you can do is making use or the template url in web access or the work item templates in the power tools to create a work item that is prepopulated with values.
What about a custom field with a display control in read-only? You can give a default value to the field and the "read-only" control prevent other to change it.
I have a site with these sections in the top nav:
About Us
News
Staff
Become a Member
Within each top nav item, is X amount of sub sections. eg:
About Us
Who We Are
Industry Stats
Annual Report
Then, within each one of those has X amount of sub pages:
About Us
Who We Are
Overview
Our History
Our Objectives
The root level top nav items (About Us) will always require the same custom fields.
The middle and bottom level pages will generally have the same content, and but will be much different to that of the root level, and so requires a different set of custom fields.
I have set the structure up so that the root items are the channels, the middle are categories, and the lower levels are just 'entries'.
My problem now, is that using a 'channel field group' on the root channel obviously filters through all categories and entries associated. So when I go to edit or publish a category landing or entry page - i am stuck by being shown the custom field group for the root landing page.
I would like it so that the end user (my client) doesnt have to see a lot of custom fields when they edit or publish a page that isnt at root channel level.
How to I set this site up, so that I can pick and choose different field groups on different pages that are within the same channel?
While you can use custom Publish Page Layouts per channel and per member group, as far I'm aware you can't present 'pages' or entries with varying Publish Layouts.
If you're using different templates for levels in your navigation, Blueprints, may be what you're looking for.
Blueprints lets you take control of your Publish Layouts [...] It is designed let you create Publish Layouts based on templates.
The taxonomy in how way you've architected your navigation and 'pages' is interesting, but not one as a client I would like to maintain or understand. For example, something as simple adding a new top-level section or page of the site should be easy, but with your methodology would require setting up an entirely new channel!
Some ExpressionEngine add-ons that may be better suited for your site and still allow you to achieve the customization you desire would be Structure, NavEE or Taxonomy — of course theres always the the native Pages Module as well.
I'm looking for an enchanced edit component that allow users to input multiple tokens (items) manually separated by some symbol, or to select them from another source.
It's something like "TO" field in outlook or facebook that allow you to input multiple recipients.
Can anyone suggest any solution?
The way we sort of do it is to use an normal button edit box and when the user clicks the button we present a separate form (which can be made to look like a drop down box if you like) with a checklist or listview with checkboxes enabled or similar. The user selects any number of the items then when the form closes we take the list of selected items and present them in the edit as a comma or semi-colon separated list. The edit itself is read-only so all interaction goes through the separate form.
But - I really don't like the whole approach (for our app) as it doesn't look good when you have many selected items and I'm looking to find a better way of showing the selection! I suppose one option is to use a read-only memo with scrollbars to show the items.
TMS has some nice components, one of which is the TCheckListEdit which might be of use.