PCGen Jira Guide - Revision history

Karianna: /* Mandatory Fields */

2011-01-07T10:20:30Z

‎Mandatory Fields

LegacyKing: /* Viewing an Existing Issue */

2010-10-27T04:43:57Z

‎Viewing an Existing Issue

LegacyKing: /* Optional Fields */

2010-10-27T04:41:12Z

‎Optional Fields

Karianna: /* Closing an Issue */

2010-10-22T14:47:34Z

‎Closing an Issue

LegacyKing: /* Entering a New Issue */

2010-07-21T01:27:51Z

‎Entering a New Issue

Karianna: /* Closing an Issue */

2010-05-26T12:02:35Z

‎Closing an Issue

Karianna: /* Resolving an Issue */

2010-05-26T12:02:14Z

‎Resolving an Issue

Karianna: /* Closing an Issue */

2010-05-26T12:01:43Z

‎Closing an Issue

Karianna: /* Resolving an Issue */

2010-05-26T12:00:16Z

‎Resolving an Issue

Karianna: /* Optional Fields */

2010-05-21T11:01:51Z

‎Optional Fields

@@ Line 37: / Line 37: @@
 * '''Summary''' - A brief description of the problem/feature you're reporting, e.g.  "Chainmail AC bonus doesn't stack with Shield"
 * '''Priority''' - You can click on the (?) button to get an explanation of the priorities, or go directly to [http://jira.pcgen.org/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels Priority Levels Help Page]
 * '''Reporter''' - This should be your username

@@ Line 62: / Line 62: @@
 There are some extra read-only fields that you may find useful when trying to track the history of changes for a JIRA:
-# '''Work Log''' - Shows a history of work logged against this issue, see [wiki.pcgen.org/index.php?title=PCGen_Jira_Guide#Logging_Work_Done]
+# '''Work Log''' - Shows a history of work logged against this issue, see [http://wiki.pcgen.org/index.php?title=PCGen_Jira_Guide#Logging_Work_Done Logging Work]
 # '''Change History''' - Shows a history of all changes made to this JIRA (including SVN Commits, Comments, Work Logged and more)
-# '''Subversion Commits''' - Shows commit messages from committers that reference this JIRA
+# '''Subversion Commits''' - Shows commit messages from svn commits that reference this JIRA
 =Editing an Existing Issue=

@@ Line 46: / Line 46: @@
 '''NOTE'''  If there is a Component option you'd like to see in the list, please drop a note to the [http://games.groups.yahoo.com/group/pcgen_webteam/ PCGen Webteam] mailing list.<br />
 '''NOTE'''  If you are entering a CODE issue then please leave this blank, the Code team will set this once the issue has been confirmed.
-* '''Affects Version/s''' - Which version of PCGen are you using?
+* '''Affects Version/s''' - Which version of PCGen are you using? [or does this issue affect, you may select multiple versions if valid]
-* '''Fix Version/s''' - If you are a team member and have a fair understanding on our roadmap, you can select which version of PCGen this will be fixed in.  Otherwise, just leave this blank, the [Tracker] team will allocate a Fix Version later.
+* '''Fix Version/s''' - Leave this blank. Fix Version will ONLY be entered when the item in question has been fixed. The Content SB and Data 2nd may assign a special Fix version for high priority versions. [Data Wishlist #1 or Data Wishlist #2, once resolved this special version will be removed from the Fix version]
 * '''Assignee''' - If you are a team member or a team member has specifically asked you to assign it to them then you can select that person here.
 * '''Environment''' - Here we'd like you to put in your Operating System, the version of Java that you're using and how much memeory you are running PCGen with
 * '''Description''' - Enter the full description of the issue here, the more detail the better!
 * '''Original Estimate''' - If you are a team member and already have a fair idea of how long it will take to fix this issue, then you can enter that here.
-* '''Attachment''' - You can attach, screenshots, PCG files, Data files etc here.
+* '''Attachment''' - You can attach, screen shots, PCG files, Data files etc here.
 =Voting for an Existing Issue=

← Older revision		Revision as of 14:47, 22 October 2010
Line 84:		Line 84:

	You can set the status to Closed if problem has been fixed and that the fix has been verified.<br />		You can set the status to Closed if problem has been fixed and that the fix has been verified.<br />
−	This ~~should be done after a release~~ is ~~cut but '''before''' the subsequent~~ release~~. e.g. If Fix Version is 5.17.3 and 5.17.3 is released then~~ the issue ~~should be closed '''before''' 5.17.4 is released.~~	+	This can occur in one of three ways:
		+	# The original reporter confirms problem is resolved
		+	# A second person confirms fix
		+	# One release cycle without another bug report on the issue

@@ Line 25: / Line 25: @@
 * You can select the CREATE NEW ISSUE in the top menu or go directly to [http://jira.pcgen.org/secure/CreateIssue!default.jspa Create Issue Page]
-# Select the Project that this issue is appropriate for.
+# [[JIRA Tracker List|Select the Project that this issue is appropriate for.]]
 # Select the Issue Type
 # Click on the Next button

← Older revision		Revision as of 12:02, 26 May 2010
Line 83:		Line 83:
	==Closing an Issue==		==Closing an Issue==

−	You can set the status to Closed if problem has been fixed and that the fix has been verified. This should be done after a release is cut but '''before''' the subsequent release. e.g. If Fix Version is 5.17.3 and 5.17.3 is released then the issue should be closed '''before''' 5.17.4 is released.	+	You can set the status to Closed if problem has been fixed and that the fix has been verified.<br />
		+	This should be done after a release is cut but '''before''' the subsequent release. e.g. If Fix Version is 5.17.3 and 5.17.3 is released then the issue should be closed '''before''' 5.17.4 is released.

@@ Line 78: / Line 78: @@
 ==Resolving an Issue==
-You can set the status to Resolved if you think the problem has been fixed.  At this stage you should also set the Fix Version to the appropriate release (usually the next Alpha or a maintenance version).
+You can set the status to Resolved if you think the problem has been fixed.<br />
 ==Closing an Issue==
 You can set the status to Closed if problem has been fixed and that the fix has been verified.  This should be done after a release is cut but '''before''' the subsequent release.  e.g.  If Fix Version is 5.17.3 and 5.17.3 is released then the issue should be closed '''before''' 5.17.4 is released.

← Older revision		Revision as of 12:01, 26 May 2010
Line 82:		Line 82:
	==Closing an Issue==		==Closing an Issue==

−	You can set the status to Closed if problem has been fixed and that the fix has been verified.	+	You can set the status to Closed if problem has been fixed and that the fix has been verified. This should be done after a release is cut but '''before''' the subsequent release. e.g. If Fix Version is 5.17.3 and 5.17.3 is released then the issue should be closed '''before''' 5.17.4 is released.

@@ Line 43: / Line 43: @@
 These fields are very useful to the PCGen team, so please do take time to fill them out as much as possible!
-* '''Component/s''' - What part(s) of PCGen does this issue affect?  '''NOTE'''  If there is a Component option you'd like to see in the list, please drop a note to the [http://games.groups.yahoo.com/group/pcgen_webteam/ PCGen Webteam] mailing list.
+* '''Component/s''' - What part(s) of PCGen does this issue affect?<br />
 * '''Affects Version/s''' - Which version of PCGen are you using?
 * '''Fix Version/s''' - If you are a team member and have a fair understanding on our roadmap, you can select which version of PCGen this will be fixed in.  Otherwise, just leave this blank, the [Tracker] team will allocate a Fix Version later.