Jira has a great and clear way of doing this when entering time estimates in the task estimate field, simply using 1 letter after the weeks (w), days (d), hours (h) and minutes (m).
By not allowing a user to enter decimals, visualizing and reading the data is much easier.
For example, if a user adds 1,50h would they mean 1 hour and 50 minutes or 1 hour ...
Try showing them visually, as they build the restriction and exemption times. With each criterion added, the timeline updates.
I'm not sure I fully understand your use case, but it sounds like users need to clearly see the results of their restrictions and exceptions. I'm focusing a little bit on how to see the outcome as feedback.
Forcing them to read ...
Standard format for time (and time intervals less than 24 hours in duration) is set by ISO 8601.
Using extended format (hh:mm[:ss]) fits best (note :!), clearly conveying time nature of the value.
From my experience, even though it says:
Decimal fractions may be added to any of the three time elements. However, a fraction may only be added to the lowest ...
I hope I am not misunderstanding your needs, but my recommendation is to do away with the exception/exclusion periods, as they are merely reinstating the default (criterion* applies) in a period of "restriction" (criterion does not apply). Intuitively it might appear simpler to say (as in your 3rd example) "The criterion should apply all year, except for a ...
Language and Regional preferences are two different things: there are english-speaking countries that use 24-hour clock and there are non-english countries that use 12-hour clock, and some use both. Moreover, how they use the 12-hour clock may differ, or they can use a completely different time format.
I think, proper solution would be change the display ...
I don't have enough reputation to comment so this answer is intended to add additional context to Astrogator's (Though I do think that Owen Hughes has provided the best answer from a UI perspective).
Astrogator's answer is misleading in that it conflates "time" (the absolute value of the time of day in a given time zone) with "duration" (the amount of time ...
Tom, how granular does this setting have to be?
Especially for less technically savvy users, providing a set of meaningful presets could already do the trick. E.g., here's the menu for setting the alert for a calendar event (taken from Fantastical for Mac):
If you click Custom…, you get to see this:
If that doesn't work, you could simply concatenate ...
Overlap of rules
I apologize if I misunderstood the ASK, but I feel this is a classic case of AND & OR operations (kind of :P).
Users add a rule (set up time period) i.e Application
Users can add another rule on top of the above rule i.e Exception, which may or may not overlap with the set time period.
Since the application and exception are closely ...
Is it necessary for your use case to know how many hours someone worked in a specific day rather than during his shift? In other words, is the value “5h18m” meaningful in your situation?
If no, then maybe you could simply have one row for each “clock in => clock out” period. As Jess Eddy mentioned in his response, it doesn’t really make sense to have a date ...
It depends on the users. Is it a form, that a user uses very often? in this case one field with the input like "6 m" or "6 h" would be a possibility. This is very fast but has to be learned. Therefore only an option if the users are powerusers.
If this is not the case, two fields could be a solution. Let the user input the duration in either a hour and a ...
Additional answer – still use decimal notation in reports
In addition to displaying individual values like 4d 1h 30m as shown in the accepted answer, it needs to be said that in context of reports (or other lists with multiple values) it would be unacceptable:
Peter 4d 1h 30m
Joan 1d 30m
In the U.S., the majority go by AM/PM and a great majority doesn’t know what to do with 0-24, unless they’ve been in the military or similar type of public service. I would definitely consider a solution that serves both depending on your audience.
Usually simplifying the copy language helps (something like "add valid time range" & "block specific dates".
A second option would be adding colors such as green (for restricted times) and red (for exception times), following the logic:
Green => go, Red =>stop
A third option is to add an icon (+ for add, - for restricting).
Best if you do all ...
If possible, try to use time intervals that are easy to calculate, and allow them to explicitly choose a delay or 'offset'.
I might not understand your use case, but it seems there is two concepts: report generation and report delivery.
I'm not sure who your users are, but words like interval and offset seem more to conform to a database model, rather ...
These timestamps should be very rare; it's just one hour in the 8760 which happen in a year's time. The hour is deliberately chosen in the night, so most people not familiar with UTC (programmers, system administrators, astronomers, military) don't need to register anything in that hour.
That said, one option might be that when a user enters an ambiguous ...
To expand on Mike M's solid suggestion, you might want to research if you can limit the number of "time intervals" to a handful of meaningful options. See the below screenshot form Apple Mail for an example.
If that'd work for the offset, too, you could also further consolidate the "Send this report" setting from a radio button pair plus text field into a ...
The problem is that you are presenting the rules, but not the result.
As a litmus test, try to answer the question: is the criterion applied on Mar 23rd?
Applies from 2019-01-01 to 2019-12-31
Except from 2019-07-14 to 2019-08-15
The following display is easier to reason about... especially as exceptions pile up:
Applies from 2019-01-01 to ...
Not sure what programs you use but excel can give you a week number based on a date, assume cell A1 has the relevant date then :
Will give :
If the date is in week 7...
the text in double quotes can be what you want but notice the space at the end...
Then just produce the relevant ones you need for the chart.
Of course if ...
Date/time formatting follows a series of conventions that are globally stated and standardized. You can find the specific time formatting for every locale in the CLDR (Unicode Common Locale Data Repository).
So, time formatting is not something you would be speculating about: there is a strict series of rules you should follow to comply with the globally ...
You could display these stretches on a timeline, something like this:
You can also mix the timeline and table layout, something like this:
Look at the timeline column showing the months. You could make a version of this that shows the shift length as a bar, with separate sub-columns for multiple days.
Proximity is an important rule in design:
"The principle of proximity is simply the process of ensuring related design elements are placed together. Any unrelated items, should be spaced apart. Close proximity indicates that items are connected or have a relationship to each other and become one visual unit which helps to organise or give structure to a ...