|
Caius Drusus Imperial DK (DC) Bragg Ironhand Orc Temp (DC) Neesha Stalks-Shadows Argonian NB (EP) Falidir Altmer Sorcr (AD) J'zharka Khajiit NB (AD) |
Isabeau Runeseer Breton Sorc (DC) Fevassa Dunmer DK (EP) Manut Redguard Temp (AD) Tylera the Summoner Altmer Sorc (EP) Svari Snake-Blood Nord DK (AD) |
Ashlyn D'Elyse Breton NB (EP) Filindria Bosmer Temp (DC) Vigbjorn the Wanderer Nord Warden (EP) Hrokki Winterborn Breton Warden (DC) Basks-in-the-Sunshine Argonian Temp |
It'd be nice, but I also consider it to be a pretty minor issue. If it'd be a super easy and quick thing for ZOS to do, then sure get that low hanging fruit and allow us to do this. If it takes any real effort, though, don't bother and focus on other things instead.
not to belabor the point, but yes. Seriously...some of the most basic guild functionality seems to be missing, and in a system that hinges on the expectation that you will be interacting with multiple guilds, having those guilds assigned priority seemingly at random or first-come-first-serve basis seems both painfully rigid and short-sighted.
The above is only one of many simple record-keeping improvements I'd like to see implemented with guild and other social functions.
Very true. From my own experience, when you're prioritizing bug fixes and functionality improvements you need to look at the available resources, the severity of the issue, whether there's a work-around, and whether it's a quick win (what I referred to as low hanging fruit earlier). Sometimes it's appropriate to prioritize quick wins over other issues, because the whole point of them is that they take very little in the way of resources (and for that you need to consider both dev and testing resources), yet they provide an improvement that users will notice and appreciate, so you can have a much faster turnaround time on them.It'd be nice, but I also consider it to be a pretty minor issue. If it'd be a super easy and quick thing for ZOS to do, then sure get that low hanging fruit and allow us to do this. If it takes any real effort, though, don't bother and focus on other things instead.
I can go with that UrQuan I've always been of the mind that good time management is key, I would think in this instance 1 programmer 1 work day is probably the benchmark to decide to do or not do this but again that depends if they only have 1 programmer then it's more like 1 programmer 5 min, and if they have 10,000 programmer it could be more like 100 programmers 10 days....I dunno the details to make that call but it would be nice icing for a really annoying ui function.
|
Caius Drusus Imperial DK (DC) Bragg Ironhand Orc Temp (DC) Neesha Stalks-Shadows Argonian NB (EP) Falidir Altmer Sorcr (AD) J'zharka Khajiit NB (AD) |
Isabeau Runeseer Breton Sorc (DC) Fevassa Dunmer DK (EP) Manut Redguard Temp (AD) Tylera the Summoner Altmer Sorc (EP) Svari Snake-Blood Nord DK (AD) |
Ashlyn D'Elyse Breton NB (EP) Filindria Bosmer Temp (DC) Vigbjorn the Wanderer Nord Warden (EP) Hrokki Winterborn Breton Warden (DC) Basks-in-the-Sunshine Argonian Temp |
Very true. From my own experience, when you're prioritizing bug fixes and functionality improvements you need to look at the available resources, the severity of the issue, whether there's a work-around, and whether it's a quick win (what I referred to as low hanging fruit earlier). Sometimes it's appropriate to prioritize quick wins over other issues, because the whole point of them is that they take very little in the way of resources (and for that you need to consider both dev and testing resources), yet they provide an improvement that users will notice and appreciate, so you can have a much faster turnaround time on them.It'd be nice, but I also consider it to be a pretty minor issue. If it'd be a super easy and quick thing for ZOS to do, then sure get that low hanging fruit and allow us to do this. If it takes any real effort, though, don't bother and focus on other things instead.
I can go with that UrQuan I've always been of the mind that good time management is key, I would think in this instance 1 programmer 1 work day is probably the benchmark to decide to do or not do this but again that depends if they only have 1 programmer then it's more like 1 programmer 5 min, and if they have 10,000 programmer it could be more like 100 programmers 10 days....I dunno the details to make that call but it would be nice icing for a really annoying ui function.
Anyway, if this were to fall into the category of a quick win/low-hanging fruit, then I'd be happy to see it implemented.