Build Tracker will receive another update after 5 PM today. The update addresses a couple of bug fixes and some enhancements to finalizing interviews and the UI.
Bug Fixes
Fix a bug that prevents user from making and saving edits to a finalized interview in edit mode.
Fix a bug in which the user cannot assign the placement date on finalizing an interviewing, without saving it first.
Finalizing Interviews
“Finalize” button will be renamed as “Add to Build Queue”.
Serial number will be required on finalizing. This ensures that the machine is at the Service Desk before it is added to the build queue.
On finalizing, the ticket’s responsibility in Team Dynamix will be reassigned to “Service Desk – CN Builds”.
The ticket’s comment will carry the machine’s serial number.
System type will be removed from the comment.
UI Enhancements
The “Software” tab of the interview will contain a button which links to the KB article listing default software for Windows and Mac builds.
“List of Default Software” button
“Last modified” time of the interview will be updated in real-time on saving. Consequently, the interview will no longer have to be reloaded.
At the end of the day on Monday, 9/10/2019, the MCS customer service number ( 78721 ) will be re-routed to the Service Desk.
This is part of the spin down of the MCS service. The MCS line receives very few calls. Most calls will be about Zoom, for which the Service Desk provides tier 1 support.
For more complex issues, please escalate to the Zoom Support team in TeamDynamix. For urgent requests (e.g. VIP conference room setup) please ask Ryan Fordham – in Milne 213C. Come say hi!
As of last week, the following groups have moved off of CN service and are now supported by UHDS IT:
Diversity & Cultural Engagement (DCE)
Cultural Resource Centers
The ONID accounts have been moved and should display with the correct IT support team in RefTool. UHDS IT have asked us to not make any changes to the computer objects yet.
Let me or Chris Sinnett know if you have questions.
Build Tracker will receive an update after 5 PM today. It’s a big one, so this is a longer post than usual. However, I order the list of changes below in descending order of importance, so read the sections “ticket search” and “asset search” first if you can’t finish the post in one sitting.
Currently, Build Tracker asks for a manual entry of ticket number when creating or cloning an interview. This is error-prone, and requires cross-checking with Team Dynamix.
Manual entry of ticket number
After the update, BT will feature a ticket search field. Searching for a ticket ID will reveal the ticket information from Team Dynamix including the title and requester.
Ticket search drop-down
Clicking on the ticket will auto-fill the ticket number text below. You must select a ticket in the drop-down to assign a ticket number to the interview.
The ticket clone dialog will also feature this search bar. It will work the same way there.
Ticket search bar in clone dialog
Asset Search
Similarly, to minimize data entry errors, asset ID entry will also be done via a search bar. Asset search will replace the asset entry fields on the AD/Cyder tab of the interview view and the build view.
Interview – AD/Cyder tabBuild
Searching for an asset by ID will reveal the asset with information from Team Dynamix, including the name, manufacturer, and model.
Asset search result
Alternatively, you can also check whether there is already an asset tied to the ticket (in Team Dynamix). Type a question mark in your query to list assets tied to the ticket:
Query ‘?’ result
Because this query actually composes of two separate queries made in succession to Team Dynamix, the process can be a little slow. Initially, you’ll likely see a “no asset found” message. Give it a second, and the asset will show.
Selecting an asset from the drop-down will also automatically populate the asset’s data to the page.
Asset’s data is populated on selection.
Because of this automatic behavior, the “populate asset data” button will be made deprecated and removed.
Notice the new kid to the block, the “add asset to ticket” button. If an asset is available in Team Dynamix, and the asset hasn’t already been added to the TD ticket, you can tie the asset to the ticket here.
Cloning an Interview
Aside from the ticket search bar, there will be other UI changes to cloning. Currently, the clone dialog provides two buttons at the bottom, “use this info” and “cancel”.
Current clone dialog
After the update, the clone dialog will feature three buttons:
Three buttons after update
These buttons are intended to provide a bit more flexibility to cloning.
More importantly, Build Tracker’s current behavior upon cloning is to switch immediately from the original interview to the clone. The new behavior will open the clone in a new tab, leaving the original in the previous tab. Furthermore, the original interview will display a confirmation dialog, including the ticket numbers of the original and clone.
Cloning confirmation dialog
Saving Interview Bug Fix
The update will fix a bug that prevents an interview from being saved when the AD Domain OU field is not filled in (in the AD/Cyder tab).
Other UI Improvements
Saving an interview will also provide a confirmation or error dialog. (If you choose to “save and clone” at the clone dialog, a save confirmation will pop up in addition to the clone confirmation).
Saving confirmation
Saving will also refresh the page to show you that the ticket has indeed been saved and to update the “Last Modified” time at the top right corner.
“Edit mode” is intended to render a finalized interview editable (to a certain extent). To clarify its usage, edit mode will not show unless the interview is finalized.
For visual clarity, the “save” button in the build view will be highlighted with an orange-red color.
Before, the development (dev) instance of BT looked exactly the same as the production (prod) instance. To distinguish between them, dev now has a red top banner and the word “sandbox” next to “Build Tracker”. Prod (the instance normally used) does not have this change.
Build Tracker’s top banner on dev
That’s all, folks! If you have questions or comments, feel free to let me know. I can be reached on Slack or by email.
