This commit is contained in:
@@ -22,58 +22,15 @@ FIRST CLIENT SOURCE CODE COMMIT JAN 3rd 2019
|
|||||||
|
|
||||||
# OUTSTANDING MAJOR AREAS TO BETA
|
# OUTSTANDING MAJOR AREAS TO BETA
|
||||||
|
|
||||||
# NOW DOING: - finishing up the must haves
|
|
||||||
make sure nice to haves or not done get cased somewhere for future v.next or whatever
|
|
||||||
figuring out the seed data adn will it suffice for widgets required once have figured out widgets required
|
|
||||||
(demand drives features not features awaiting demand)
|
|
||||||
|
|
||||||
|
|
||||||
# SEEDING ISSUES
|
# SEEDING ISSUES
|
||||||
|
|
||||||
|
|
||||||
seeder, make a few wo that are not completed in time in each month
|
seeder, make a few wo that are not completed in time in each month
|
||||||
|
|
||||||
seeder make reminders and reviews for all users, just random scattering for now to future month ahead at least one per day to show off schedule and widgets
|
seeder make reminders and reviews for all users, just random scattering for now to future month ahead at least one per day to show off schedule and widgets
|
||||||
seeder wo need new fields and generate data to show off and test kpi widgets and features
|
|
||||||
Add completed date to workorder, should be set when a closed status is set
|
|
||||||
used for numerous kpi stuff
|
|
||||||
adjust seeder to work with it so the closed state created date matches wo completed date
|
|
||||||
|
|
||||||
Also, can we calc "time to respond" based on anything extant or should there be some kind of additional field / system for that
|
|
||||||
i.e. maybe a workorder status is also a response status like some are closed??, then a mirror first response field like completeddate
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
# WIDGETS
|
# WIDGETS
|
||||||
|
overdue, not scheduled should have status flags dislay
|
||||||
Should LIST types have a fixed limit of maximum records returned??
|
|
||||||
i.e. no more than 500 or something?
|
|
||||||
if reaches the limit then says "500 limit reached" in the list as the last item?
|
|
||||||
|
|
||||||
- Widgets to make for beta in order of priority
|
|
||||||
**MUST HAVE***
|
|
||||||
|
|
||||||
|
|
||||||
LIST work orders filtered by status (case 1974)
|
|
||||||
this *does* make sense because it can be hyper specific to something like a "waiting for parts" status so
|
|
||||||
if that is useful to a user then can see that list
|
|
||||||
needs limit, could bring in thousands if not careful
|
|
||||||
criteria:
|
|
||||||
wo status required
|
|
||||||
timespan
|
|
||||||
tags wo, woitem
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**NICE TO HAVE**
|
|
||||||
(these are not triaged yet)
|
|
||||||
|
|
||||||
avg time or time breakdown by % of overdueness of workorders
|
|
||||||
i.e. 10% of overdue were x days overdue etc
|
|
||||||
avg time in each status by time period / tags
|
|
||||||
this could cover response time as they can just designate a status as unresponded or new
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -22,7 +22,11 @@
|
|||||||
<v-list-item :key="i" two-line :to="'/svc-workorders/' + item.id">
|
<v-list-item :key="i" two-line :to="'/svc-workorders/' + item.id">
|
||||||
<v-list-item-content>
|
<v-list-item-content>
|
||||||
<v-list-item-title
|
<v-list-item-title
|
||||||
><span class="text-h6 primary--text">{{ item.serial }}</span
|
><span class="text-h6 primary--text"
|
||||||
|
>{{ item.serial }}
|
||||||
|
<v-icon :color="statusColor(item.laststatusid)"
|
||||||
|
>$ayiFlag</v-icon
|
||||||
|
></span
|
||||||
><span class="ml-4">{{ $ay.dt(item.completebydate) }}</span>
|
><span class="ml-4">{{ $ay.dt(item.completebydate) }}</span>
|
||||||
<span class="ml-4">{{ item.name }}</span></v-list-item-title
|
<span class="ml-4">{{ item.name }}</span></v-list-item-title
|
||||||
>
|
>
|
||||||
@@ -130,7 +134,10 @@ export default {
|
|||||||
return {
|
return {
|
||||||
obj: {},
|
obj: {},
|
||||||
context: false,
|
context: false,
|
||||||
localSettings: {}
|
localSettings: {},
|
||||||
|
selectLists: {
|
||||||
|
wostatus: []
|
||||||
|
}
|
||||||
};
|
};
|
||||||
},
|
},
|
||||||
computed: {},
|
computed: {},
|
||||||
@@ -142,6 +149,12 @@ export default {
|
|||||||
await this.getDataFromApi();
|
await this.getDataFromApi();
|
||||||
},
|
},
|
||||||
methods: {
|
methods: {
|
||||||
|
statusColor: function(statusId) {
|
||||||
|
let ret = this.selectLists.wostatus.filter(z => z.id == statusId);
|
||||||
|
if (ret && ret.length > 0) {
|
||||||
|
return ret[0].color;
|
||||||
|
}
|
||||||
|
},
|
||||||
showContext: function() {
|
showContext: function() {
|
||||||
this.localSettings = window.$gz.util.deepCopySkip(this.settings);
|
this.localSettings = window.$gz.util.deepCopySkip(this.settings);
|
||||||
this.context = true;
|
this.context = true;
|
||||||
@@ -187,10 +200,25 @@ export default {
|
|||||||
/////////////////////////////////
|
/////////////////////////////////
|
||||||
//
|
//
|
||||||
//
|
//
|
||||||
async function initWidget() {
|
async function initWidget(vm) {
|
||||||
await fetchTranslatedText();
|
await fetchTranslatedText();
|
||||||
|
await fetchWorkorderStatusList(vm);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
async function fetchWorkorderStatusList(vm) {
|
||||||
|
let res = await window.$gz.api.get("work-order-status/list");
|
||||||
|
if (res.error) {
|
||||||
|
vm.formState.serverError = res.error;
|
||||||
|
window.$gz.form.setErrorBoxErrors(vm);
|
||||||
|
} else {
|
||||||
|
vm.selectLists.wostatus = res.data.all;
|
||||||
|
let noStatus = window.$gz.form.getNoSelectionItem(true);
|
||||||
|
noStatus.color = "#eeeeee";
|
||||||
|
noStatus.locked = false;
|
||||||
|
noStatus.completed = false;
|
||||||
|
vm.selectLists.wostatus.unshift(noStatus);
|
||||||
|
}
|
||||||
|
}
|
||||||
//////////////////////////////////////////////////////////
|
//////////////////////////////////////////////////////////
|
||||||
//
|
//
|
||||||
// Ensures UI translated text is available
|
// Ensures UI translated text is available
|
||||||
|
|||||||
Reference in New Issue
Block a user