SourceForge to JIRA Transition Training

Transcription

1 SourceForge to JIRA Transition Training The following training material is intended for OSCAR Service Providers and Community members to transition from SourceForge to Atlassian s JIRA software. Atlassian is an enterprise software suite that develops products for software developers, project managers, and content management. OSCAR EMR s long term plan is to use a combination of Atlassian s tools to manage OSCAR s source code, Confluence for developer/user content management, and bitbucket as OSCAR s code repository. OSCAR EMR s transition from SourceForge to JIRA will only affect the Bug and Feature Request Tracker module of SourceForge. All other modules of SourceForge (including mailing lists) will not be transitioned at this time. While viewing issues/features from JIRA will still remain public, you will be required to create an account to post bug reports or feature requests. Sign up for an account Go to 1) Click Create an account'. 2) Enter your address and the verification code. 3) Enter your details and follow the instructions. 4) Click the Sign up button to create your account. For an overview of the JIRA Application, we recommend you check out Atlassian s online training videos: Meet JIRA Software: JIRA in a Nutshell: Intro to JIRA: to jira You can also find a JIRA User s Guide*on the Atlassian Documentation website which provides basic information including: Exploring the JIRA workspace Browsing a project Working with JIRA Issues JIRA Basic Concepts user s guide html *Not all of the features that you find on the website will apply to OSCAR EMR s use of JIRA. OSCAR EMR SF to JIRA Training Rev /11/2016 1

2 OSCAR Issue and Feature Tracker Overview Main Screen The main screen is called the Dashboard and will look like this upon initial log in: Project Introduction window An Assigned to Me window that displays issues that have been assigned to you Activity Stream window This menu allows you to: Quick search for project information access the Help and Other Information features manage user profiles. Project In the top navigation bar, click the Projects drop down list > View all projects > OSCAR Issue and Feature Tracker to access OSCAR s new Bug Report and Feature Tracker. This will load the project summary page, which displays recent activity and lets you easily track the status of issues in this project. This project is to be used for both bug reports and feature tracking. Information on filtering the project is available below. OSCAR EMR SF to JIRA Training Rev /11/2016 2

3 Issues JIRA issues are the building blocks of the JIRA software project. The issues in the OSCAR Issue and Feature Tracker refer to both bugs and feature requests. These are called issue types. Therefore, creating a ticket in SourceForge is equivalent to creating an issue in JIRA. You can access an issue in JIRA from a search result or a list of issues using the dashboard navigation and sidebars (refer to the section called Searching for Issues ). All issues, regardless of version, belong to the OSCAR Issue and Feature Tracker (project key = OSCAREMR). The project key becomes the first part of the issue keys (e.g. OSCAREMR 1010, OSCAREMR 1011 etc.). Further, bugs are labelled as and feature requests are labelled as... Creating an issue 1. Click Create at the top of the screen to open the Create Issue dialog box (see next page). 2. Select the Project (OSCAR Issue and Feature Tracker) and Issue Type in the Create Issue dialog box. Bug or New Request issue types only 3. Complete all appropriate fields Priority numbers are listed from 1 9, with 5 being the Default priority. Refer to the additional info about customized fields by clicking the symbol. The Bug Report Template remains as a requirement in JIRA. You must complete the following fields: o Preconditions, Steps to Reproduce, Expected Result, Observed Result The Feature Request Template also remains and the following fields are required: o Milestone, Change Description, OSCAR Interaction points, Integration risks, Risks if not incorporated, Minimum Testing and Training requirements, and time estimate. 4. Go to: an issue html to learn more about creating issues in JIRA 5. Note about versions: There are 3 versions in the JIRA project: Master, RELEASE 12.1 and RELEASE 15. Anything that is not 12.1 or 15 will not get a version in the migration. The Affects Version/s field in the bug report template must include at least one of those versions. o If the commit is being made to the RELEASE_15_BETA branch, it must also be committed to master. The Fix Version/s will always be None. When creating a new Feature Request in JIRA, the Milestone options only include Main Trunk, , OSCAR 14, or OSCAR 15. OSCAR EMR SF to JIRA Training Rev /11/2016 3

4 Bug Report Template: Feature Request Template: OSCAR EMR SF to JIRA Training Rev /11/2016 4

5 Issue View Below is an example of an issue within the OSCAR Issue and Feature Tracker Project. Project name and issue key Various tasks/actions on the issue Creator of the issue and Update date in JIRA Issue Information (if issue created in SF, it will show here) Description of issue from template OSCAR EMR SF to JIRA Training Rev /11/2016 5

6 Issue Details and Template Fields The table below describes all of the fields within an issue and the Bug Report/Feature Request Templates. Field Description Project The parent project to which the issue belongs. It should always be the OSCAR Issue and Feature Tracker project equivalent to the OSCARMcMaster project in SourceForge. Issue Type Either Bug or New Feature. Reporter The person who entered the issue into the system Assignee The person to whom the issue is currently assigned. Priority Priority level which indicates the issue s importance. 5 is the Default. 8 and 9 are most critical. OSCAR Build Date and Date of the OSCAR Build for the issue and name of the Build. Tag Client Browser and OS Dropdown list of user Browser and OS of client environment. Affects Version/s Either Release 12.1 or Release 15. Fix Version/s Always None Migrated Issues from SF SourceForge Link Original ticket on SourceForge. SourceForge Reporter Creator of the original SourceForge ticket. SourceForge Assigned to Assignee of original SourceForge ticket. SourceForge Date The date that the ticket was posted on SourceForge. created Issue Workflows OSCAR EMR SF to JIRA Training Rev /11/2016 6

7 A JIRA workflow is the set of statuses and transitions that an issue goes through during its lifecycle. Below is the workflow for the OSCAR EMR Issue and Feature Tracker Project. Notes that the workflow is the same bug reports and feature requests. Issue Status Definitions Open New issues enter the system here. Issues remain in this status until they have been reviewed and verified, identified as insufficient information to reproduce, or rejected. (All statuses can transition to Open) Open Accepted Issues progress from Open status to Open Accepted if the content follows the template provided and the issue has been accepted. Pending Open issues which do not follow the submission template or require additional information to reproduce are set to pending after review. If additional information is not provided after the allotted amount of time progress to Open Rejected. Open Rejected Erroneous reports or feature reports submitted as issues are placed in this status. After reporter confirms or the allotted amount of time elapses will progress to Closed Rejected. (All statuses can transition to Open Rejected) Open Fixed Issues progress to this status when there is a submitted fix pending commitment to appropriate branch and/or confirmation of fix. (All statuses can transition to Open Fixed) Open Wont Fix Issue has been validated, however, the developers have determined to either leave it due to readily available workaround, the issue being eliminated by upcoming changes, or an unreasonable amount of work on a soon to be unsupported branch. OSCAR EMR SF to JIRA Training Rev /11/2016 7

8 Open Works For Me Issues which pass review but cannot be reproduced by a developer. Requires additional supporting information from submitter to be re evaluated. Should progress to Closed Works For Me after an allotted amount of time passes without re evaluation. Open Duplicate Issue is already in the reporting system. Progress to Closed Duplicate after the allotted amount of time without the submitter providing additional information. (All statuses can transition to Open Duplicate) Closed Duplicate Issues which have been closed from open duplicate. Closed Out Of Date Issues which are closed due to their respective branch no longer being supported or part of curation efforts based on submission timestamps or last edited timestamps. (All statuses can transition to Closed Out Of Date) Closed Fixed Issues which have been closed from open fixed by having their fix confirmed. Closed Works For Me Issues which have been closed from Open Works For Me. Closed Wont Fix Issues which have been closed from Open Wont Fix. Closed Rejected Issues which have been closed from Open Rejected. Searching for Issues 1) Click on Issues from the main panel at the top of the screen. 2) Under Issues options click on Search for issues (see image on next page) that will open a window from where the user can locate issues and perform multiple functions. 3) Enter the criteria for the search. You can search against specific fields and/or search for specific text. a. To search against specified fields, you need to select the fields then specify the fields values that you want to find. b. If you want to search using additional fields as criteria, click More and tick the desired fields. For more information about searching for issues, go to: searching html OSCAR EMR SF to JIRA Training Rev /11/2016 8