Views that follow your team
Managers and team leads can save focused views, then adjust people, groups, and priorities as their teams and responsibilities change.
Starting with TeamDynamix
Experience TeamDynamix
in a whole new way - AI first.
Turn ticket data into
a clear next step.
See which work needs attention, where requests slow down, and who’s carrying the load. MineMyMine brings your TeamDynamix tickets and recorded history together so you can understand the work behind the numbers.
See the lightbulb? Work through it with AI. Ask what a view means, follow the evidence, and talk through what to check next.
Bring a clearer picture to your team. Then act in TeamDynamix.
Follow the walkthroughUse cases
Six ways to put your tickets to work.
Focus effort. Learn from success.
Compare historical ticket trends to find where resources may help most - and where your teams and processes are already working well.
Shape targets around the work
Work with AI to tailor ticket groupings - then discuss proposed SLA targets for different customer groups or kinds of work.
See patterns in new ways
Explore ticket history with AI. Compare groups, time periods, and journeys, then plan new visualizations that could reveal patterns worth investigating.
The right view for the right people
Administrators assign permission views to specific people, limiting which saved tickets they can read. Give each person the visibility their work needs.
Find work you could prevent
Investigate recurring requests, handoffs, and reopenings with AI - find opportunities for better documentation, training, or changes to the service itself.
Find your starting point
See where the work
needs you.
Start with the current picture: open work, ticket statuses, and the groups carrying it. When something stands out, follow it into a focused view. Each view helps answer the next question.
- Find Tickets
- Narrow your scope, sort the results, and inspect individual ticket details.
- Needs Attention
- Find high-priority, unassigned, old, and stale tickets that need a closer look.
- Overview
- See open work, this week’s activity, statuses, ticket types, and busy groups.
- Weekly Flow
- Compare weekly ticket intake with how many tickets from each week have since closed.
- Ticket Age
- See how old open tickets are and when they were last updated.
- Teams & Owners
- Compare active work across groups and people, including unassigned work.
- Ticket Patterns
- Explore ticket journeys, response times, holds, handoffs, and reopenings through recorded history.
- Low Activity
- Spot missing ownership and groups or services with little open work in your selected scope.
How It Works
Give the numbers their context.
Before deciding where work is getting held up, choose whose work you’re looking at and check the collection date. Then follow the records that explain the picture.
Your selected scope
Focus on a team, owner, status, priority, service, or date range. Carry your selected scope into the charts and comparisons to keep the evidence relevant.
Full ticket records
Collect ticket details, descriptions, comments, replies, and available source history from TeamDynamix. Each collection includes the records accessible through your signed-in account.
The recorded journey
Follow available updates, replies, status changes, and ownership changes, including source events between collections. Saved snapshots separately preserve how the overall workload looked at each collection.
Needs Attention
Which tickets deserve
a closer look?
Start with the work most likely to need a conversation: high-priority, unassigned, aging, or stale tickets. Narrow the scope to your team or service and choose where to look first.
- Focus on the team, status, service, priority, or period that matters.
- Compare assigned and unassigned work within that scope.
- Read individual ticket details when a result needs a closer look.
A flag gives you a starting point. Next, look at who owns the work and what the ticket records say.
Teams & Owners
Who’s carrying
the work?
Compare active work by group and owner, including unassigned tickets. See where work is concentrated and who to include in the conversation. Ticket counts give you context; ask the people doing the work what sits behind them.
Ticket Age
What has been waiting?
What has gone quiet?
Once you know where the work sits, compare when open tickets arrived and when they were last updated. Use age and activity to choose requests worth following up, then inspect their details before deciding why they are waiting.
Low Activity
What might you
be overlooking?
Look beyond the busiest groups. Explore services with little open work and tickets with missing ownership in your selected scope. A quiet view is a reason to check the context; it does not establish that a team has spare capacity.
Weekly Flow
Is incoming work
reaching closure?
Now look across weeks. Compare how many tickets arrived with how many from that same week’s intake have reached closure. Both lines use the ticket’s creation week; the closure line includes tickets that closed later.
- See how the volume of incoming work changes across weeks.
- See how many tickets from each creation week have reached closure.
- Use your chosen filters to focus the comparison.
Ticket Patterns
Where did the
journey slow down?
When a week’s tickets deserve a closer look, follow their recorded journey: first response, status changes, handoffs, holds, reopenings, and completion. Choose a creation week to explore where those tickets spent their time and which events need investigation.
- Compare response and completion times, time in each status, and time spent on hold.
- Trace ownership changes, unassigned intervals, reopening cycles, and recorded activity.
- Compare recorded timing with source deadlines and see how backlog levels change across saved collections.
Recorded history includes available source events between collections. Saved snapshots preserve how the workload looked at each collection.
Find Tickets
Check the ticket
behind the pattern.
A chart points you toward a question. The ticket gives you the detail to investigate it. Open a record in your collection, read the request and replies, and follow its available status and ownership history before drawing a conclusion.
Work through the evidence
Work through the
question together.
You can bring AI into the conversation at any point. Ask what a chart means, have an answer explained more simply, or talk through what to inspect next. Follow up as your understanding changes, and check the ticket evidence together.
- Select a chart's lightbulb to ask “What am I looking at?” and get an explanation grounded in that view.
- Choose New chat to start a fresh conversation.
- Resume a saved conversation from Your chats.
Leave with a ticket to review, a question for its owner, or a clearer next step. Make ticket updates in TeamDynamix; MineMyMine reads the source records without changing them. Your saved chats keep the conversation available for your return.
From a question to a useful next step
See Sarah bring it together.
Leadership wants to know why requests are taking so long. Follow Sarah, a fictional IT service manager, as she explores the workload with a colleague, asks AI for help, checks an individual ticket, and turns what she learns into a conversation with her team.
Read the video transcript
A normal morning
Sarah: Hey, I'm Sarah. I look after IT service operations at Cedar Valley University. These are the people who keep classrooms, laptops, and access requests moving. My job? Help them figure out where we can make the biggest difference.
Got a minute?
Peter: Sarah, got a minute? Leadership's asking why requests are taking so long.
Sarah: Yeah. The team's working hard already. Before we start moving work around, let's see what actually needs a closer look.
Same screen
Peter: I've got three reports open. They don't quite agree.
Sarah: Okay. Let's look together in MineMyMine. We'll check this snapshot's date first. Collection's still running, so this is our starting picture. Here, the open tickets are grouped on this chart. Let's ask what we're looking at.
A little help
Peter: Just click the lightbulb?
Sarah: Yep. 'What am I looking at?' Then, 'What next?' It points us toward New, the biggest category here. That gives us somewhere to start.
Say it simply
Peter: Can it say that a little more simply?
Sarah: Absolutely. 'Explain like I'm five.' There we go. A photo of the work at one point in time. Useful for getting our bearings. We'll need to look closer to understand the waiting.
Who should we talk to?
Peter: Let's see which teams have the work.
Sarah: Teams and Owners. This helps us work out who to talk to. I'd want their side of the story before asking them to take on anything else.
Which requests need a look?
Peter: What about the requests people have been waiting on?
Sarah: Let's look at Ticket Age. When did requests come in, and when were they last updated? That gives us another way to decide which ones deserve a closer look.
Read the request
Peter: Can we see the actual requests behind this?
Sarah: Right here. Find Tickets. Look at this first one: 'Service sign-in interruption.' Emergency.
Read the whole row
Peter: Oh. That sounds bad.
Sarah: And it's already closed. Glad we checked. Let's ask the service desk whether this is connected to what people are calling about, and what still needs following up.
A useful next step
Peter: So, a quick call before the meeting?
Sarah: Exactly. With a ticket in front of us. And remember, you can always check with AI using the lightbulb. It helps us work out what to ask next.
The conversation continues
Peter: I'll keep this open.
Sarah: Hi, it's Sarah. Have you got a minute to look at a request with me?
Explore MineMyMine
MineMyMine, by VroomITs. Turn TeamDynamix ticket data into a clear next step. Interested? Let’s talk. Visit minemymine.com or email contact@vroomits.com.
Make it part of your working day
Choose how AI
works with you.
The same questions can travel with you. Work inside MineMyMine or connect a compatible desktop AI client through MCP, then return to saved views and conversations as the work develops.
Choose your AI
Your provider.
Your model.
Choose how AI joins that work. Use the provider and model that fit your environment; your questions and relevant ticket context go to the connection you select.
- Use familiar online AI services, such as OpenAI’s ChatGPT or Anthropic’s Claude.
- Connect through a corporate or institutional AI gateway.
- Use on-premises or locally connected AI compute, including compatible specialized AI devices, for information too sensitive to leave the enterprise. Keep processing and data routing inside your organization.
Prefer working in your own AI workspace? Bring MineMyMine into the conversation with MCP.
MCP integration
Keep the conversation where you work.
Bring your model to the data.
Work inside MineMyMine with the AI provider and model you choose. Ask about your TeamDynamix tickets, explore patterns, and inspect the records behind an answer.
Bring the data to your AI.
MCP (Model Context Protocol) connects MineMyMine’s saved data and supported tools to a compatible desktop AI client on Windows. Explore tickets, reports, charts, and recorded history from that client, using the tools you enable.
On-premises or in the cloud.
Choose an AI connection that fits your environment. Use an organization-hosted endpoint or a cloud provider, with the access and tools you choose to enable.
Ready for the next question
Pick up the next question with context.
Collect the full ticket record
Collect full ticket records, descriptions, comments, replies, and recorded history through your signed-in TeamDynamix account. Collection starts when you open MineMyMine; load fresh data when you need it. An interrupted collection preserves your last complete saved view.
Save a view worth returning to
Choose your filters, apply them, and save your scope, priorities, and display preferences. Return to the views that matter as your ticket collection grows.
Protect your saved work
Create and restore password-protected backups of your saved tickets, recorded history, views, and display settings. Accounts and sign-in credentials are excluded.
A little more context
MineMyMine FAQ
What can I do with MineMyMine?
Understand what needs attention in your TeamDynamix workload and why. Compare teams, spot aging or unassigned work, follow recorded ticket journeys, and inspect individual records. Work through questions with AI, then bring the evidence to your team and make any ticket updates in TeamDynamix.
How do I get started?
Sign in to TeamDynamix in Edge with MineMyMine Companion enabled, then open the MineMyMine desktop app. Let it collect the tickets your account can access, choose your AI connection and model, and ask your first question. This website is a product tour; you work with your own tickets in the application.
Can I choose my AI provider and model?
Yes. Choose familiar online AI services such as OpenAI’s ChatGPT or Anthropic’s Claude, a corporate or institutional AI gateway, or compatible on-premises or locally connected compute. Pick a model available through your connection. Signed-in ChatGPT connects through Codex; On-prem AI and Custom use an OpenAI-compatible HTTPS endpoint provided by you or your organization.
Can I use MineMyMine from my own AI client?
Yes. Configure a compatible desktop AI client for MineMyMine’s local MCP connection. The client can inspect your saved ticket collection through the supported tools you enable, using its own chosen model. MineMyMine’s built-in AI keeps its separate provider and model selection.
Can sensitive data stay inside my organization?
You can keep AI requests and processing inside your organization by using an endpoint hosted and routed entirely within its environment. Your questions and relevant ticket context go to the connection you select. For restricted data, use an organization-approved internal endpoint and confirm its hosting and routing with your IT team.
Can I inspect the whole ticket, including its history?
Yes. Open each ticket in your collection to inspect its full details, description, comments, replies, and recorded history available to your signed-in TeamDynamix account. That includes updates, status changes, and ownership changes between collections. Saved snapshots separately show what the overall workload looked like at collection time.
Can I pick up where I left off?
Yes. Reopen a conversation from Your chats to continue it, or choose New chat for a fresh start. Conversations are saved after an answer or when you leave a chat with messages. You can also save your filters, priorities, and display preferences as a view to return to later.
Will MineMyMine change my TeamDynamix tickets?
No. MineMyMine reads your ticket data so you can explore it and understand the work. When you decide a ticket needs an update, make that change in TeamDynamix.
How do I keep my ticket data up to date?
Collection starts when you open MineMyMine. Use Load fresh data whenever you need an updated view. If a collection is interrupted or incomplete, your last complete saved view stays available. Check the collection date when reading the results.
Can I back up my saved work?
Yes. Create a password-protected backup of your saved tickets, recorded history, views, and display settings. Restoring a backup replaces that saved workspace data after you confirm. Accounts and sign-in credentials are excluded from the backup.
Does a blank value mean nothing happened?
Not necessarily. A missing recorded value is different from a measured zero. Read it alongside the ticket details, your selected scope, and the collection date before drawing a conclusion.
Bring your question
Bring a real workload question.
Which tickets need attention? Where has work slowed down? Start with the question your team needs to answer. Explore it with MineMyMine and AI, check the records, and leave with a clearer next step.