Functional Tests

Actions to be taken before starting the Issue Reminders Cloud Test:

First, the application needs to be purchased from the Marketplace and installed on the user's Jira. (FIG.1)
After the Issue Reminder is installed, it should appear under the "Manage Apps" section. (FIG.2)
If these conditions are met, the reminder can be used by navigating to the Issue View. (FIG.3)

FIG.1

FIG.2

FIG.3

Preconditions for Issue Reminders Cloud Test:

First of all, there are 3 types of admin options for Issue Reminder. In order to start testing this feature, 3 different users are required who are opened from different browsers and can see separate projects within the same team. These are as follows:
Global Admin: A global admin is someone who is always an admin in the relevant projects and is also a member of admin groups such as jira-admins-fatmauzundemir, org-admins, etc., as seen under User Management > Groups. These users have all kinds of permissions related to projects and can make changes from the configuration section. The checks that need to be done for a user to qualify as a global admin can be found on the pages shown in the screenshots below.

Since the user is a Global Admin, the expected outcome in the Settings section is:

FIG.1

Even if the user is a Global Admin, the expected outcome for a specific project is:

FIG.2

Project Admin: A project admin is a person who is not a global admin but is granted admin privileges for specific projects. These users only have configuration permissions within the Project Settings section. The checks that need to be done for a user to qualify as a project admin can be found on the pages shown in the screenshots below.

Since the user is a Project Admin and not a Global Admin, the expected outcome in the Settings section is:

FIG.3

When the user is a Project Admin for a specific project, the expected outcome is:

FIG.4

Non-Admin: Non-admin users do not have any configuration permissions. These users can only view or use the relevant areas according to the properties assigned by the admins. The checks that need to be done for a user to qualify as a non-admin can be found on the pages shown in the screenshots below.

Since the user is a Non-Admin, the expected outcome in the Settings section is:

FIG.5

When the user is a Non-Admin for a specific project, the expected outcome is:

FIG.6