{"id":49,"date":"2024-12-18T08:10:52","date_gmt":"2024-12-18T08:10:52","guid":{"rendered":"https:\/\/fullstacknotes.netblocs.com\/?p=49"},"modified":"2024-12-18T10:02:36","modified_gmt":"2024-12-18T10:02:36","slug":"react-developer-scenarios-3-jira-github-and-your-first-react-task","status":"publish","type":"post","link":"https:\/\/netblocs.com\/fullstacknotes\/react-developer-scenarios-3-jira-github-and-your-first-react-task\/","title":{"rendered":"React Developer Scenarios-3: Jira, GitHub & Your First Task"},"content":{"rendered":"
\n
\"\"<\/figure><\/div>\n\n\n

Scenario<\/h3>\n\n\n\n

You have just joined a new MERN project called \u201ceticaretvadisi.\u201d After setting up VS Code on your computer and downloading the project files locally, you successfully managed to run the project. Now, the Team Leader has assigned you your first task: correcting word errors in the language files. Additionally, you\u2019ve been asked to address task SVW-1076, which also contains simple word corrections, alongside this task.<\/p>\n\n\n\n

You are using Jira for project management, and the project is maintained on GitHub.<\/p>\n\n\n\n

To-do List:<\/h3>\n\n\n\n
    \n
  1. Create a task in Jira.<\/li>\n\n\n\n
  2. Commit the changes in the code to GitHub, following the naming convention of the task you created in Jira.<\/li>\n\n\n\n
  3. Apply the code changes for the SVW-1076 task and commit them to GitHub.<\/li>\n\n\n\n
  4. Once the changes are complete, open a Pull Request (PR) and request the Team Leader to review and merge the changes.<\/li>\n<\/ol>\n\n\n\n

    Steps to Apply:<\/h2>\n\n\n\n

    Step 1: Create a Task in Jira<\/h3>\n\n\n\n

    While there are different ways to create a task, the basic process is as follows:<\/p>\n\n\n\n

      \n
    • Log in to Jira and navigate to the Kanban page of your project.<\/li>\n\n\n\n
    • Click the \u201cCreate\u201d button in the top menu.<\/li>\n\n\n\n
    • In the window that opens, fill in the following details:\n
        \n
      • Project Name<\/li>\n\n\n\n
      • Issue Type: Task (or Bug, based on the instruction)<\/li>\n\n\n\n
      • Status: Open<\/li>\n\n\n\n
      • Description: Briefly describe the task.<\/li>\n\n\n\n
      • Reporter: Assign yourself as the reporter.<\/li>\n\n\n\n
      • Priority: Medium<\/li>\n\n\n\n
      • Assignee: Select yourself.<\/li>\n\n\n\n
      • Sprint: Choose the active sprint of the project.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

        It\u2019s important to correctly fill out the assignee<\/strong> and sprint<\/strong> fields. Without selecting the sprint, other developers and your Team Leader won\u2019t be able to track your task.<\/p>\n\n\n\n

        After creating the task, Jira will automatically assign it a name. For this example, let\u2019s assume your new task is named SVW-1088.<\/p>\n\n\n\n

        Step 2: Create a New Branch for the Project<\/h3>\n\n\n\n
          \n
        • Open the project in VS Code and open a new terminal.<\/li>\n\n\n\n
        • Update the main branch:<\/li>\n<\/ul>\n\n\n\n
          <\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
          git<\/span> <\/span>pull<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
            \n
          • Create a new branch with the task name you created in Jira:<\/li>\n<\/ul>\n\n\n\n
            <\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
            git<\/span> <\/span>checkout<\/span> <\/span>-<\/span>b<\/span> <\/span>SVW<\/span>-<\/span>1088<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
            Step 3: Make the Necessary Changes and Commit Them<\/h3>\n\n\n\n
              \n
            • Make the necessary changes in the code.<\/li>\n\n\n\n
            • Commit the changes.<\/li>\n<\/ul>\n\n\n\n
              You can do this either through the command line or via the Source Control tab by clicking Commit and then Sync. What\u2019s important is that you follow the commit message conventions set by your Team Leader or company. For example, your commit message could follow this format:<\/p>\n\n\n\n
              (Task Name) (category of action): (brief description of the action)<\/code><\/pre>\n\n\n\n
              An example:<\/p>\n\n\n\n
              <\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
              SVW<\/span>-<\/span>1088<\/span> <\/span>fix<\/span>:<\/span> <\/span>corrected<\/span> <\/span>wrong<\/span> <\/span>words<\/span> <\/span>in<\/span> <\/span>en<\/span> <\/span>lang<\/span> <\/span>files<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
              If you\u2019re using the command line:<\/p>\n\n\n\n
                \n
              • Stage the changes:<\/li>\n<\/ul>\n\n\n\n
                <\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
                git<\/span> <\/span>add<\/span> <\/span>.<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
                  \n
                • Commit the changes:<\/li>\n<\/ul>\n\n\n\n
                  <\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
                  git<\/span> <\/span>commit<\/span> <\/span>-<\/span>m<\/span> <\/span>"SVW-1088 fix: corrected wrong words in en lang files"<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
                    \n
                  • Push to GitHub:<\/li>\n<\/ul>\n\n\n\n
                    <\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
                    git<\/span> <\/span>push<\/span> <\/span>origin<\/span> <\/span>SVW<\/span>-<\/span>1088<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
                    Step 4: Make the Necessary Changes for the Other Task and Commit Them<\/h3>\n\n\n\n
                    In cases where tasks are simple and short, it may not be necessary to create a new branch for each task. Sometimes, multiple small tasks can be completed and committed within a single branch.<\/p>\n\n\n\n
                    The important thing to remember here is that each commit should be made with the corresponding task name. Continuing from the example, once you complete the SVW-1076 task within the SVW-1088 branch, your commit should refer to SVW-1076, not SVW-1088. For example:<\/p>\n\n\n\n
                    SVW-1076 fix: corrected wrong words in tr lang files<\/code><\/pre>\n\n\n\n
                    This way, within the SVW-1088 branch, you can push commits related to both SVW-1088 and SVW-1076.<\/p>\n\n\n\n
                    If the integration between Jira and GitHub is correctly set up, after committing your changes, the status of both tasks in Jira should automatically change to REVIEW<\/strong>.<\/p>\n\n\n\n
                    Step 5: Open a Pull Request (PR) and Submit for Review<\/h3>\n\n\n\n
                    Create a Pull Request (PR) on GitHub:<\/p>\n\n\n\n
                    Usually, when you navigate to the GitHub page for your project, you will see a button to create a Pull Request related to your task. You can click this button to create the PR. Alternatively, you can follow the steps below to create the PR manually:<\/p>\n\n\n\n
                      \n
                    1. Go to GitHub and open your project.<\/li>\n\n\n\n
                    2. On the left-hand side, click on the Pull requests<\/strong> tab.<\/li>\n\n\n\n
                    3. Click the New pull request<\/strong> button.<\/li>\n\n\n\n
                    4. In the new page, set the base branch as main<\/strong> and the compare branch as SVW-1088<\/strong>.<\/li>\n\n\n\n
                    5. Write a description for the PR. You can use the same message as your commit message.<\/li>\n\n\n\n
                    6. Click Create pull request<\/strong> to create the PR.<\/li>\n\n\n\n
                    7. On the right-hand side of the page, fill out the following fields:\n
                        \n
                      • Reviewer<\/strong>: Select your Team Leader or the person responsible for reviewing the task.<\/li>\n\n\n\n
                      • Assignee<\/strong>: Select yourself.<\/li>\n\n\n\n
                      • Type<\/strong>: For this example, choose Bugfix<\/strong>. If it\u2019s a new feature, choose Feature<\/strong>.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
                        Notify the Team Leader:<\/h3>\n\n\n\n
                        a. After creating the PR, if the task statuses do not automatically change to REVIEW<\/strong> after committing, update the task status manually in Jira. Notify your Team Leader to review and merge the PR via Slack or email.<\/p>\n\n\n\n
                        Step 6: Close the Task<\/h3>\n\n\n\n
                        Once the PR is merged, close the task:<\/p>\n\n\n\n
                          \n
                        1. After the PR is merged, go to Jira and mark the task as Done<\/strong>.<\/li>\n\n\n\n
                        2. In more professional teams, this process works as follows: After the Team Leader merges the PR, the Jira task is automatically moved to QA<\/strong> or manually by the leader. The testing team will test the changes, and if everything is correct, they will change the status to Done<\/strong>, completing the process.<\/li>\n<\/ol>\n\n\n\n
                          Congratulations!<\/strong> You\u2019ve successfully completed your first task as a software developer.<\/p>\n","protected":false},"excerpt":{"rendered":"
                          Scenario You have just joined a new MERN project called \u201ceticaretvadisi.\u201d After setting up VS Code on your computer and downloading the project files locally, you successfully managed to run…<\/p>\n","protected":false},"author":1,"featured_media":51,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,31],"tags":[27,29,28,14,30],"class_list":["post-49","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-react","category-react-developer-scenarios","tag-developer-scenarios","tag-github","tag-jira","tag-react","tag-task"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/posts\/49","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/comments?post=49"}],"version-history":[{"count":3,"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/posts\/49\/revisions"}],"predecessor-version":[{"id":111,"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/posts\/49\/revisions\/111"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/media\/51"}],"wp:attachment":[{"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/media?parent=49"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/categories?post=49"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/netblocs.com\/fullstacknotes\/wp-json\/wp\/v2\/tags?post=49"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}