Remove menu option for specific selected values? - tableau-api

Is there a way to remove the option to select a menu link for specific fields?
For example I have a dashboard that has details of each users action and a few of those users are actually an automated system. So the few that are part of the system do not need to be reviewed as those are always automatic.
I want to only allow this menu selection for actual users and not the few "accounts" that are part of an automated system.
The kind of menu link on selection I am talking about.
Is it possible to remove this menu link for only specific values in a column?

I don't think it's possible - am fascinated to know if someone comes in with a way to do it - so one option to consider is renaming to "Daily Details - ignore for Bot 1 & 2" so the users are aware they should do nothing.

Related

Remove Turn Editing on for courses in Moodle/Totara

I have a bunch of custom user groups. I need to change the permissions for one of the user groups so they don't see "Turn editing on" button or link. I figured out a way to do this in a reports section. I can't figure out a way to do this for course section.
I deactivated manage blocks and manage activities and that removed the button on all of the sections except courses. I tried to deactivate update course and a bunch other course related capabilities with no luck. Did not see any sort of manage courses capability.
Any help would be appreciated as I just inherited this site and have had no previous experience with Moodle.
Totara version 2.7
Moodle version 2.2.11
Do you want to this by code or configuration? If you want to do this, simply by configuration, just make a new user group for them "Site administration->User->Permissions->Define Roles", give them the ones you want them to have. Then assign the users in question this role. They should not see the buttons in question.

How can I track metrics on who does code reviews in JIRA?

I'm working on a project that's got a great JIRA setup and awesome buy-in of everyone for the agile development process. The issue I'm having is that tickets stack up in code review. I'd like to be able to see who code reviewed what, much like I can see who has closed out which tickets.
I know that metrics are there to be used for good and not evil, so I want to do this to ensure that people spending time code reviewing are properly credited instead of that time not being recognized at all.
Currently, everyone who does code review assigns themselves to the ticket (which is unassigned upon being placed into the "Ready for Review" workflow state), so at some point there is a record of them working on it. Is this a good way to track the reviewers and is there a way to get aggregate information this after the fact? If not, is there a better way of representing this information in JIRA?
Thanks!
A simple solution would be to add a custom field called 'Code Reviewer' of type select a user. You would be able to search on that and report on it.
You could workflow it so that when the issue is transitioned out of your 'Code Review' status a window pops up containing only the "Code Reviewer' custom field to be completed.
What you need to do:
Create a new custom field - this is done in the 'Issues' configuration menu. Ensure your custom field uses the 'select a user' type.
https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field
Create a new Screen - this is also done in the 'Issues configuration menu. On your new screen you need to make sure that the only field that is visible is your new custom field.
https://confluence.atlassian.com/display/JIRA/Defining+a+Screen
Edit your workflow. Find the transition from out of 'Code Review' and associate it with your custom screen.
https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
The result will be that when a user transitions out of 'Code Review' they will have the custom screen pop-up. They can then select the name of the person who did the code review and this will be populated in the custom field.

Best Product Listing Option for Concrete5

I'm going to be creating a Concrete5 website that will feature product listings. The listing system must offer all your typical ecommerce features, minus the ability to purchase items. It's strictly for browsing purposes only.
For example:
- Browse by category
- Search products
- Listings/results page with thumbnails and brief information (title, description, price in US/CAD, manufacturer, maker, etc.)
- Products single page (with detailed information, attributes and gallery/images)
All the things you'd expect to find in a listing system.
My issue is I can't find a specific add-on for something like product listings. This leaves me thinking that it may be best to use the e-commerce add on and do my best to hide anything related to the cart/payment process. That way it could just be used for everything else it offers.
What are your thoughts on this? Is there a better option?
Thanks for the advice!
Use the page list block. It has everything you need except for searching. But, in essence, that's what your requirements call for -- listing of pages.
Create a page type for your "product". The "brief information" can be in the Content block, or you can set as attributes. You'll probably want to make some minor changes to the block's view (by creating a new template) that displays the image as you want, the proper attributes, etc. Something similar to http://www.concrete5.org/documentation/how-tos/designers/styling-the-page-list-block/
There are several adanced page list blocks in the marketplace. You might want to start with those.
Right creat Page type.
After creat Page attributes.
Add a block page_list create a template for it and filter by attributes.
You can even use ajax to filter.
http://www.weblicating.com/doku/doku.php?id=cheatsheet/#.UbR7P0BmiSp
U can find here about page_list or read documentation Concrete5.

iPhone Settings Menu - creating a list that allows user to add, edit and delete items

I am looking to create a settings menu feature that allows users to add, edit and remove items from a list. In adding an item to the list, the user will then be prompted to add some further sub-data such as name, value etc. The list should only allow one item to be selected. As far as I can see this is similar to, but beyond the capability of the PSMultiValueSpecifier, in terms of the user adds/edits/deletes and sub-data being added.
Similar functionality is implemented in the ‘Choose A Network’ section of the iPhone’s Wi-Fi settings but I am not sure how this is done. In this, users can add a new network and then specify security type, password etc.
Any ideas how I might go about achieving this?
Do a search in sample code regarding UITableView (In iPhone dev center or inside Documentation), I am sure I have seen that kind of sample ;)

Design ideas for multi-select items from a long list

I'm developing a system in which I need to select, from a long list os customers, some to which an specific (batch) action will be executed. For example, I want to select "John", "Peter" and "Steve" and click the "delete" button. No more than 5 customers will be selected.
The problem is that, since there're more than 500 customers, listing all isn't a good option. So far I did an AJAX search that shows just the customers that meet the criteria, but which multiselect way you recommend?
My best idea so far is a below this list in which I could either drag-and-drop the users I want to select or double click them
Any better ideas/examples?
Thanks
I don't know whether you're using jQuery, nor whether your site's design vocabulary is suited to it -- but this jQuery autosuggest plugin is excellent.
+1 for ksr's autosuggest find. I would use this in conjunction with a list box. The user types in the autosuggest input field and when they select an item it adds it to a list box. They can then add additional names via the same method, and submit the list when they've added all the names.
I would go for the pattern used by eBay. They probably did some usability research. You can find more info here: http://quince.infragistics.com/Patterns/Multiple%20Selection%20from%20a%20Large%20List.aspx