Configuration items in OTRS’ CMDB are not to be deleted for consistency reasons – old tickets, changes, services etc. depend on them. But how do we get them out of our view once they are scrapped?
We can use the deployment state of the items as additional marker and modify the display with plain CSS and a little bit of Javascript.
Example list of computers
List of items
Some days ago I found a quite interesting article on Change Management. But there is a better way than to work with Templates for Word or Excel is to use a Change Management System like the Change Management Module of OTRS::ITSM.
Right now our Development Team works on the interface of OTRS::ITSM to modernize it also, like the base Framework to a new CSS based frontend.
"Bugs", courtesy of US National Archives.
Today we released the second beta in our cycle before we release the stable release of OTRS 3, which will land 1st of December, 2010. The first beta was released on Monday 2nd of August. So what has been done in the three weeks between beta1 and beta2? A lot, but we’re absolutely not done yet.
First of all, I wanted to mention that in the almost ten years that the OTRS project exists, we never before received this much feedback on the first beta! That is great. Many thanks for all your ideas, suggestions, and of course, bug reports. Keep them coming!
So we fixed a lot of bugs, the full list is here: http://source.otrs.org/viewvc.cgi/otrs/CHANGES?revision=1.1319&view=markup&pathrev=rel-3_0_0-b2. You can go and check if your favorite bug has been fixed already.
There are still lots of bugs open, as of today we have 74 bugs open against OTRS 3 (actually, 38 if you don’t count the enhancement requests) and that is a lot. So there’s still plenty of work to do. You are welcomed to look at the reported bugs, provide feedback, attach test cases, and of course attach patches! In the upcoming couple of weeks we will work hard to fix even more bugs for the next beta.
The dashboard finally gains more functionality provided by the community:
Please share your own Dashboard Modules but also your ideas with us? What do you think about a Twitter post module, a world clock, a map displaying where your customers with open tickets are located and so on…..
follow:
