LegacyKing: Created page with "Data '''F'''eature '''REQ'''uest Process: Open JIRA Tracker - Anyone with a JIRA Account may open a Feature Request for Data Feature Requests are to add additional materials or..."

2011-12-10T09:55:46Z

Created page with "Data '''F'''eature '''REQ'''uest Process: Open JIRA Tracker - Anyone with a JIRA Account may open a Feature Request for Data Feature Requests are to add additional materials or..."

New page

Data '''F'''eature '''REQ'''uest Process:

Open JIRA Tracker - Anyone with a JIRA Account may open a Feature Request for Data

Feature Requests are to add additional materials or improve how something LST does.

Example: Say I have an ability that says "Allows the user to 1/day per 3 levels to increase their attack by +1 per 2 levels"
The user could request that those be changed to show the actual values changing it to:

"Allows the user to 4/day to increase their attack by +6"

STEPS:
* Open [Someone Submitted a request - Data Team Determines it's a legitimate request and will mark it for 'In-Progress']
* In-Progess [Determined to be legitimate - Monkey has assigned themselves and are working on it]
* Resolved [Data Monkey has added the issue - the Original Reporter is notified. Set FIX VERSION as the next Release Version]
* Closed [Reporter is allowed to CLOSE the issue if they confirm the issue has been implemented and are happy with the results, otherwise a Tracker Monkey, or Data 2nd/Silverback will close after a few Release Cycles]

NOTE: You may fix an issue and skip the IN-PROGESS to the RESOLVED [If addressing another Reporters issue] or CLOSED [IF and ONLY IF you are adding a Feature and you are the Reporter].

Data FREQ process - Revision history

LegacyKing: Created page with "Data '''F'''eature '''REQ'''uest Process: Open JIRA Tracker - Anyone with a JIRA Account may open a Feature Request for Data Feature Requests are to add additional materials or..."