登録: 2017-09-06 03:26
最終更新: 2017-09-14 00:22
Ticket System Documentation
チケットの履歴 - 12 件中 3 件表示 [古い履歴も表示する]
2017-09-06 03:26 更新者: earnie
2017-09-07 00:03 更新者: earnie
Keith, please review the documentation for creating tickets. Close this ticket if good.
2017-09-11 23:34 更新者: keith
I'd like to make a few refinements, but how do I get to a page where I can edit it? I can't see any appropriate reference links.
2017-09-11 23:43 更新者: earnie
2017-09-12 02:00 更新者: keith
Got it, thanks! So, we need a firstname.lastname@example.org request, to get rid of the incomprehensible "Notice for submit this type tickets:" nonsense at the top, (above our top level heading), or at least have it translated to grammatically correct, and intelligible English. Ideally, it should not be there at all, so that we can put a sensible instruction below the heading; otherwise, I guess the intended meaning is "Instructions for submitting tickets".
2017-09-12 04:05 更新者: earnie
2017-09-12 17:19 更新者: keith
I've now tidied it up, to my satisfaction. Just one further comment, before closing: I appreciate that we are abusing the "component" and "milestone" classifications, but have we not got the logical associations back-to-front?
2017-09-12 21:46 更新者: earnie
I basically followed what we have at SF with modification where required due to field differences.
We could go back to having multiple ticket types but we avoided that at SF. One thing we cannot control with OSDN is the status of the ticket beyond Open, Assigned and Closed.
2017-09-13 04:35 更新者: keith
Given that a "milestone" implies a measurement of progress, I've always thought that package itemisation under that field name was rather incongruous, whether on SF.net or here; the "component" field name just seems like a better fit, for that particular classification. So, we're now abusing "milestone" to represent what "component" more logically implies, and then we're abusing "component" to represent what might be better described as "category". Certainly, "category" could equally well be described as "type", which then implicitly suggests having separate trackers for each such "type", (as seems to be the design intent of OSDN trackers); remind me: why did we subsume four separately "typed" trackers into one, on SF.net?
2017-09-13 07:00 更新者: earnie
IIRC, it was because everyone chose the Bug type and it wasn't easy to move it.
It seems though that OSDN can change the Type if we want to go back to using it as was intended.
OSDN associates component to a package and can be associated to the FRS.
Milestone on SF could be loosely renamed (not all headings took on the rename) and I had renamed it as Group.
Looking at the Ticket Type Admin page we can set a Type as private so only those with rights can use them but they are not able to be publicly viewed. Components can be tied to a particular "Technician", i.e. you, Cesar or me but that is just a default. The way I created the milestones with an open ended date field causes it to be used only for filtering the list and for counts of tickets.
How do we want to proceed?
2017-09-13 23:51 更新者: earnie
Thinking about this a little more this morning. It makes sense to me to move what I have as a Milestone to the Component field. If we do that we would need to use the Type field for the various types but I'm only wanting an admin to decide if it is a Bug, Feature, etc and I don't know that we can set the type as Private but have the user still comment in the ticket or even get to it. I'll create a private type and test with my test user "mingw" account.
2017-09-14 00:22 更新者: earnie
So moving an issue to a Private Type causes the user who entered the ticket to receive an error of "Invalid ticket id" when trying to access the ticket. A link to the ticket is listed on the users Home page even after it becomes a private type. Given this we don't want to misuse the Type field for this purpose. We can have the various types of ticket but we will need to live with the misuse by the user.
追記/更新 #37495 (Ticket System Documentation)