Feature Request - Multiple Assets in tickets

litechforce

Hello,

I think a good feature to have would be to be able to assign more than one asset to a ticket. Some issues affect multiple assets, and having to create separate tickets for each asset for the same issue.

JosephWithCOR

@litechforce That has been a reoccurring request since forever (>1400 forum posts) ago with multiple requests merged into a single string. https://forum.itflow.org/d/217-feature-request-multiple-assets-on-a-ticket

The request is on their roadmap itflow-org/itflow637

The way we use ITFlow, if a task touches multiple computers like say a change request, it becomes a project. Bulk add the assets, tie to project, edit to correct the subject line and other missing information, and bulk close after verifying the work.

But there are lots of low count computer projects. Swapping an old for a new. Rebuilding and having to reset a computer account on a DC (d/217). Setting up a department shared printer. Deploying a foot switch on all the computers in evidence.

But, some companies production metrics are based on ticket counts / time spent. The more tickets I plow through in a month, the more productive I look. The more productive I look, the easier it is to justify my meager existence…

YMMV…

(Your mileage may vary…)

johnny

We added multiple assets per ticket a week ago, currently sitting in the develop branch Stable should be next out at the end of the week