Tag Info

Hot answers tagged

14

JIRA, the enterprise ticket management system, recently added the ability to 'Configure Fields' when editing a ticket. This means that all the fields are still readily accessible, but the user only has to see the things they're interested in. They did a couple smart things when they rolled this out. First, they made this setting sticky on a per-user ...


14

One of the factors to be considered in this is performance. If it takes the system a few extra seconds to bring up the complete result set than I would steer away from it. And even if the time it takes to bring up both screens is the same, I would go with Option 1 because the blank table acts as a type of prompt for the user to enter in some sort of search ...


10

In your situation, I like option 2 better. I think what you are really building is a 'Practices View'. Text based search is just one feature of this 'Practices View'. It looks like you have filtering, sorting and a few other features as well. As you mention in your question, option 2 also removes the need for the user to enter a search term before they ...


5

I have a similar set up for a test environment and a production environment. I found myself accidentally adding test data to the live database. So I wanted to make sure that it was easy to identify which server I was on. I could glance at the address bar, but it was too easy to forget. I wanted the differences to be minimal but obvious. I chose to add a ...


4

As a user, I hate running into limits after I've invested time. For example, say I've uploaded 50 pictures thinking I can make a slide show with all 50 pictures. If there is a limit of 10 slides, and I don't discover this limit until I go to add the 10th or 11th slide, I'm gonna be unhappy. So, my first suggestion is to indicate from the beginning what the ...


4

You could hide the fields by default for the user roles that wouldn't fall into the "power user" bucket & show by default for the power user roles. You could also add the option to 'always show' or 'always hide' after the user has toggled show/hide.


3

Well you could think about applying miller's columns: http://en.wikipedia.org/wiki/Miller_columns I've seen very nice implementation of this pattern in deviantart.com with a search input above selector, screenshot:


2

I assume that the reason Admin user would need to know current roles is because this UI will also Remove Roles from the User. One option is to make two different operations "Assign Roles" and "Remove Roles". Because this is more natural operation than "Edit" roles . While might seem like two operations are now required, I think clarity and ability to ...


2

It's good for the front end and back end interfaces to have some degree of parity from a branding point of view (particularly since in your particular example, the same users will potentially see both interfaces) but that's not to say they should have exactly the same look and feel. They are after all serving different purposes and aimed at (initially) ...


2

I've built an admin interface recently, but I didn't ask for input. Frankly I should have, but I think it's fair to consider the use of administration interface the same as standard user interface. It's just got more navigation paths and configuration options. Having said that, following is a list of things that I'd consider mandatory if I were launching ...


2

I'd second your opinions on option #2. I see several advantages There's information to act upon right away. User gets a complete sense of this overall screen area. Various UI elements are in harmony. Action components are relevant to "available information". It saves an action...and that's a lot!


1

The site should respond according to the authorizations set by the super user. This means that the deleted user should subsequently get "not authorized" responses from any links (s)he clicks that require the authorization that was just deleted. This should happen immediately and should not be dependent on a session time out or (re-)login. Of course any ...


1

The path I took for a similar problem was close to what Google does for gmail, drive, etc. List the first X number of users in a table (w/ pagination) and put a search field at the top that filters the table. Check boxes or clicking/tapping the users selects them and another button adds them to a group. This may be a bit heavier than what you're looking ...


1

Your current suggestion works, but it is a bit vintage if you don't mind me say so. Another way is to use auto-suggest and comma separated fields to assign users. It takes less space of the UI and uses search technologies instead of selecting from one to the other column.


1

I'm not sure an icon here would be better than simply using the word "Banned" or "Approved" along with red and green colors. Also I would consider the word "Approved" here instead of "Unbanned." The reason is that it's a positive way of explaining the status. It's not banned. It's allowed. It's approved. The word "Unbanned", meanwhile, is a negative way of ...


1

I would separate the option of add a new one completely and add the edit option for each element. In the way that inside of each category section we have an "Add new one" button at the beginning of the list and a "edit" button per bike. In this way is easier to edit a specific bike and even easier add a new one.


1

The standard in my experience is to allow users select their own color based on log in ID. As you can see in this screen shot, I have admin and normal user access to 3 different versions of the same system (production, test & Development) for a total of 6 different access/environments. I have seen a few systems that don't allow for this, but most do. ...


1

It seems, you need to implement Master/Detail pattern. Master/Detail screen pattern can be vertical or horizontal. Ideal for creating an efficient user experience by allowing the user to stay in the same screen while navigating between items. Horizontal layout is a good choice when the user needs to see more information in the master list than just a ...



Only top voted, non community-wiki answers of a minimum length are eligible