Task 2-Adding Tasks feature (Marks: 55) At the end of this specific task, students should be able to: . Create and work

[answerhappygod]

Task 2 Adding Tasks Feature Marks 55 At The End Of This Specific Task Students Should Be Able To Create And Work 1 (150.33 KiB) Viewed 16 times

Task 2-Adding Tasks feature (Marks: 55) At the end of this specific task, students should be able to: . Create and work with Loops Handle and manipulate strings (Learning Units 4 and 5). It is good practice to leave your main branch as your long live branch, this means that the code on this branch is always in perfect working order and tested. We make use of feature branches in order to ensure that any code we push to GitHub does not break our main branch. You can create a feature branch by running the following command. git checkout -b KhanbanTasks (you can use any branch name) ** You are welcome to make use of GitHub desktop or your IDE to push code to GitHub if you are not comfortable with using the command line. You can now add the following functionality to your application: 1. The users should only be able to add tasks to the application if they have logged in successfully. 2. 3. The applications must display the following welcome message: "Welcome to EasyKanban". The user should then be able to choose one of the following features from a numeric menu: Option 1) Add tasks. a. 21; 22:23 2022 b. Option 2) Show report - this feature is still in development and should display the following message: "Coming Soon". C. Option 3) Quit 4. The application should run until the users selects quit to exit. 5. Users should define how many tasks they wish to enter when the application starts, the application should allow the user to enter only the set number of tasks. 6. Each task should contain the following information: Task Name The name of the task to be performed: "Add Login Feature" Task Number Tasks start with the number 0, this number is incremented and autogenerated as more tasks are added. Task Description A short description of the task, this description should not exceed 50 characters in length. The following error message should be displayed if the task description is too long: "Please enter a task description of less than 50 characters" OR "Task successfully captured" if the message description meets the requirements. Developer Details The first and last name of the developer assigned to the task. Task Duration Task ID The estimated duration of the task in hours. This number will be used for calculations and should make use of an appropriate data type. The system must autogenerate a TaskID which contains the first two letters of the Task Name, a colon (:), the Task Number, a colon (:) and the last three letters of the developer 2022 assigned to the task's name. The ID should be displayed in all caps: AD:0:INA Task Status The user should be given a menu to select the following task statuses from: To Do Done Doing 7. The full details of each task should be displayed on the screen (using JOptionPane) after it has been entered and should show all the information requested in the table above in the following order: Task Status, Developer Details, Task Number, Task Name, Task Description, Task ID and Duration; 7. The total number of hours across all tasks should be accumulated and displayed once all the tasks has been entered. Create a Task class that contains the following messages: Method Functionality Method Name Boolean: checkTaskDescription() This method ensures that the task description 21; 22; 23