AP-258 - Getting issue details... STATUS AP-455 - Getting issue details... STATUS

App Objective:

Follow-up enables you to generate reminders for all issues that have had no action for an elapsed time period. This applies to assignee and users that are tagged on the comments for which there was no follow up action. Reminders can be reviewed as reports or sent via email to the assignee or tagged users.

Functional Requirements:

The functional requirements of the Follow up application:

1. Basic search functionalities with Project, Issue type and Time Elapse
2. Use JQL filter to select the range of issues and also predefined time elapsed values.
3. App should create Time elapsed custom field and should use it for calculation.
4. The report should show the username, number of days elapsed and the total number of issues in which the user is mentioned (predefined 'time elapsed categories (>=2days, >=7 days and >=14 days)). Consolidated report for each user with time elapsed categories.
   
5. Exporting the report in the form of CSV / PDF.
6. Saving the query for the scheduler - Limit the query count based on the Jira count specified in the Jira server settings.
   
7. Sending emails as the reminder for all the users who are mentioned in the issue - Each user gets the report of issues they are mentioned on (on the comments).
8. Scheduling the report based on particular time.
9. Report generation will be restricted based on the user project permission.
10. Users can save their filters and generate a report based on the saved filter. 

Technical Limitations:

The technical limitations for the application

1. The basic and advanced JQL should include time elapsed custom field in the query.
2. Displaying all the issues in the report screen is not possible due to issue count(If the Count is > 10000) Proposed solution on the count we can have hyperlink on the issue count that can take us to the issues view page(Export option for all the issues in CSV) - Give hyperlink to see issues in issue navigator and limit issue display based on the issue count limit as set in Jira.
   
3. Once the user triggers the report the following actions will performed

             * Search query execution based on parameters project, issue type and time elapsed

             * Create tables depends on  the query data

             * Apply Filter logic in the table(users, time elapsed and issue keys)

             * Export options based on the parameters users,time elapsed and issue key

             * Delete the table after export

             * If scheduler is enabled trigger the step 1(Search query execution based on parameters project, issue type and time elapsed) on the scheduled time

       4. Including the time elapsed function JQL function.

       5. Time elapsed will be calculated function based on the time stamp of the issue

       6. We can only share the query we can't send the report to anyone from UI

       7. The plugin can't access the DB directly to fetch data(Rest API or Java classes should be used), Jira cloud restricts DB access. Need to verify the data complexity when running the query, storage of the data in local db/other formats and updates whenever query is triggered.

To do Activities :

The To-Do activities for the follow up application

1. Checking how to add the Time elapsed function.
2. Identify the user mentioned in the activity (Latest comment).
3. Calculate the time elapsed from the last activity(Latest comments)
4. Explore implementing the project permission for query sharing

Functionality of Follow Up App Version 1

Please find the attachment here for the functionality of the first version of Cloud Follow Up App V1

Draft Timing Plan for App Development:

Phase-1 development:  AP-258

@Jay Karmarkar – To-do:

Related Jira Issues: