On this post, we will learn how to add a new field to store the date and time when an incident/event happened, this information is critical in order to have a better picture of the impact of that event in our customers and in the platform.
Also it is used to have a reference about how long took that incident until it been fixed
Jira offer 2 type of date fields : Date and Time Stamp
For this example we will use Timestamp field due that it allow us to select Date/Time, also will use the bug type of ticket
Example : Add a Timestamp
1- Go to Project Setting / Issue Types / Bugs
2- Drag and Drop the custom field Timestamp and place it just below the Summary
3- Set a proper name for this field
4- Set it as Required, this data is mandatory on the creation of a Bug ticket
5- I won’t suggest to click on “Set to current time by default” for this case. We need that the creator of the ticket set the time when the incident happens, it is a key data for further analysis.
Then you will see the new field on the Create screen as below as mandatory:
Once filled it will store the Date and Time of the event.
On Edit screen ticket it can be updated if is needed
from now we have an extra information that can helps us to generate reports with a metric about the range of date/time where happens more often incidents along the last week/month/quarter for example.
4 Responses
Python.11 Rather, class-allocated slots are used primarily to save space; if you’re going
to create many instances of a class and all instances are going to have a reference to the same object–say, a pool of shared
resources–you can save the cost of each instance having its
own reference by making the slot class-allocated.
And a sub-subclass may then redefine it back to :class slot, so all
instances of that class will again share a single
slot. He graduated high school in Maine in 1987 and then worked
to begin a career in top-level sport. White was able to get involved in the
UFC early on and use his knowledge to push the sport to a new level.
In 2005, a reality show was created titled The Ultimate Fighter, which also helped the sport to become even more popular.
Thus, every method must specify &key even if it doesn’t specify any &key parameters.
Hi there, tbis weekend iis pleasant inn suppor of me, sinjce thyis ime i am readung thos wonderful
informative piece oof writig her at my house.
Howdy very cool blog!! Guy .. Excellent .. Amazing .. I’ll bookmark your site and take the feeds also?
I’m satisfied to seek out numerous useful info here
within the publish, we want develop more techniques on this regard, thanks for sharing.
. . . . .
You don’t have to worry about the class precedence list for methods and slots inherited from only one superclass or another.
The advantage of using auxiliary methods is that it makes it quite clear which methods are primarily responsible for implementing the
generic function and which ones are only contributing
additional bits of functionality. Of course, if you’re going to rely on a coding convention–that every method calls CALL-NEXT-METHOD–to ensure
all the applicable methods run at some point, you should think about using auxiliary methods instead.
Thus, if you want to be able to reuse the code that prints the savings-account part of the statement, you’ll need to break that code into a separate
function, which you can then call directly from both the money-market-account and savings-account print-statement methods.
The more proxy components are located between client and server, the more is the latency’s part in the response time.
So Common Lisp uses a second rule that sorts unrelated superclasses according to the order they’re listed in the DEFCLASS’s direct superclass list–classes earlier in the
list are considered more specific than classes later in the list.
The problem is that while you can use CALL-NEXT-METHOD to
call “up” to the next most specific method, namely,
the one specialized on checking-account, there’s no way to invoke a particular less-specific method, such
as the one specialized on savings-account.