| Anonymous | Login | Signup for a new account | 2010-09-06 15:24 UTC | ![]() |
| Main | My View | View Issues | Change Log | Roadmap | Summary |
| View Issue Details [ Jump to Notes ] | [ << ] [ >> ] | [ Issue History ] [ Print ] | |||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0000044 | GEMS - Guild Event Management System | Characters | public | 2006-06-10 12:44 | 2009-07-08 19:09 | ||||||
| Reporter | Ni | ||||||||||
| Assigned To | Ni | ||||||||||
| Priority | none | Severity | feature | Reproducibility | always | ||||||
| Status | assigned | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 0.1 BETA | ||||||||||
| Target Version | Fixed in Version | ||||||||||
| Summary | 0000044: Application form for applying to a guild | ||||||||||
| Description | Make a long list of needed information. Let each guild decide which information they think is "mandatory", "optional", "hidden". This would make applying easier and much more streamlined. A in-system message could be generated for the class officer(s) and optionally an e-mail. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
Relationships |
||||||
|
||||||
Notes |
|
|
(0000039) Ni (administrator) 2006-06-28 11:00 edited on: 2006-06-28 11:02 |
To use this function, you must have the character created already. Make a link both from "Character list" and from the guild (front) page. If you press the "Apply for this guild" and have no chars, of course make a link to "Character create" page :) |
|
(0000045) Ni (administrator) 2006-07-04 15:00 |
To limit the DB entries, maybe make a set list of questions per game... the GMs of each game can suggest new questions - which all guild will be able to include in their application. Default will of course be to hide the new options. Sharing the questions serves at least 2 purposes. First of all it's less data to store (instead of 100 full custom entries per guild), but secondly it will also make GMs give eachother good ideas, and thereby make "the perfect app." quicker. |
|
(0000196) Ni (administrator) 2007-06-09 21:36 |
It should be possible to simply fill out an application for each character you have. You don't even have to apply for a guild - but you should be able to choose maybe these different status: Unguilded - applying Unguilded - not looking Unguilded - looking Guilded - applying Guilded - not looking Guilded - looking This opens up for a general page per server with all chars looking for a guild or whatever related to "applications". |
|
(0000205) Ni (administrator) 2007-06-19 17:02 |
When an application is accepted the character must be listed for easy access to the rest of the guild. An obvious place would be under "Member / List" - maybe a sub page to this. On the menu there should also be a clear indication of how many applications are pending (visible). This should be made in blue parenthesis and possibly a link to take you directly to the new subpage. |
|
(0000243) Ni (administrator) 2007-12-11 11:50 |
On the front page of a guilds homepage it should be listed what they need in classes - if any: Class 1: A, B, C, D. Class 2: A, B, C, D. ... Class 8: A, B, C, D. Where: A = Needed number of characters B = Number of pending applications C = No. of accepted apps. D = No. of rejected apps. Each ABCD can have different view/edit rights per level in guild. Pending apps. could even be readable by the public. This calls for more access levels at the guild option page. |
|
(0000244) Ni (administrator) 2007-12-11 16:50 |
Be careful not having redundant data stored in both the old character table and the new table(s) for storing application user data. The status of an application should be stored only in one place. Each character can then have multiple rows in the new table(s) where their Chars.ID is the key. |
|
(0000312) Ni (administrator) 2009-05-16 14:49 |
Make members of a certain rank capable of voting YES / NO for applications. Preferably with a reason, so it's easier to make a sound judgement later. Officer can then decide to use the votes and reasons when making the final decision. Maybe even make the application public, so other users can comment on the person's application. This MUST of course be an option for the applicant, since he/she could already be in a guild, hence not interested in showing the public he/she is looking elsewhere. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2006-06-10 12:44 | Ni | New Issue | |
| 2006-06-10 12:44 | Ni | Status | new => acknowledged |
| 2006-06-28 09:56 | Ni | Summary | Application form for applied to a guild => Application form for applying to a guild |
| 2006-06-28 09:56 | Ni | Description Updated | |
| 2006-06-28 11:00 | Ni | Note Added: 0000039 | |
| 2006-06-28 11:02 | Ni | Note Edited: 0000039 | |
| 2006-07-04 15:00 | Ni | Note Added: 0000045 | |
| 2007-01-22 15:11 | Ni | Status | acknowledged => assigned |
| 2007-01-22 15:11 | Ni | Assigned To | => Ni |
| 2007-01-22 15:11 | Ni | Relationship added | related to 0000027 |
| 2007-06-09 21:36 | Ni | Note Added: 0000196 | |
| 2007-06-19 17:02 | Ni | Note Added: 0000205 | |
| 2007-12-11 11:50 | Ni | Note Added: 0000243 | |
| 2007-12-11 16:50 | Ni | Note Added: 0000244 | |
| 2009-04-21 19:43 | Ni | Status | assigned => confirmed |
| 2009-04-21 19:54 | Ni | Assigned To | Ni => |
| 2009-05-16 14:49 | Ni | Note Added: 0000312 | |
| 2009-05-16 14:49 | Ni | Status | confirmed => assigned |
| 2009-05-16 14:49 | Ni | Assigned To | => Ni |
| 2009-07-08 19:09 | Ni | Category | Accounts => Characters |
| Copyright © 2000 - 2010 MantisBT Group
Time: 0.2294 seconds. memory usage: 13,924 KB |