Explore topic-wise InterviewSolutions in .

SECURITY SETTING for any issue is defined or say set either at the time of creation of the issue or while editing the issue. The basic reason for security setting is to restrict the user access to the issue so that not all USERS are able to WORK on that issue. Security setting also allows the access of the issue to the member of chosen security LEVEL.

Security setting for any issue is defined or say set either at the time of creation of the issue or while editing the issue. The basic reason for security setting is to restrict the user access to the issue so that not all users are able to work on that issue. Security setting also allows the access of the issue to the member of chosen security level.

JIRA Schema CONSISTS of the following:

• Workflows
• ISSUE types
• CUSTOM fields
• Screens
• Field CONFIGURATIONS
• Notifications
• Permissions

JIRA Schema consists of the following:

BUGZILLA : 

• It is an Open SOURCE
• Using Bugzilla might be little complicated for few due to grouping users and granting permissions
• Bugzilla allows you to show/hide the whole custom field or specific values based on the VALUE of some other field
• Bugzilla’s has a powerful advanced search option
• Unlike JIRA, Bugzilla allows users select the initial status of a new issue.
• Bugzilla has only one link type: Blocks/depends and a Bug ID custom field

JIRA :

• It is a commercial tool.
• For some using JIRA would be more convenient than Bugzilla
• JIRA ENABLES conditional configuration based only on Type fields and Project.
• JIRA lacks advance-level search options. JIRA has flexible JQL language (JIRA Query Language). It enables you to build ARBITRARY boolean expressions.
• Unlike Bugzilla, JIRA enables you to define multiple workflows which are applied based on the issue’s Project and Type.
• JIRA has configurable link types with user-defined semantics. JIRA enables to link an issue to any other entity outside JIRA.

Bugzilla : 

JIRA :

An “issue collector” enables you to EASILY embed a JIRA feedback form into your own web site.This helps WEBSITE VISITORS to LOG issues into JIRA through our website. To use JIRA feedback form, visitors to our website do not need a USER account in JIRA.

An “issue collector” enables you to easily embed a JIRA feedback form into your own web site.This helps website visitors to log issues into JIRA through our website. To use JIRA feedback form, visitors to our website do not need a user account in JIRA.

For Agile project to CREATE user stories in JIRA, follow below steps:

• Issue type -Epic and Issue type – STORY linked to it. In order to do so, in the ‘Create Issue’ page, go to “Configure FIELDS” and select “Epic link” field to be INCLUDED in the issue creation screen.
• Or you can have a product backlog by creating a MAIN User story and having various sub-tasks under it.

For Agile project to create user stories in JIRA, follow below steps:

Under Audit LOG, you can SEE all the DETAILS about the issue CREATED, and the changes made in the issues.

Under Audit Log, you can see all the details about the issue created, and the changes made in the issues.

The events are classified in TWO a System EVENT (JIRA defined events) and Custom event (User defined events). An event describes the STATUS, the default template and the notification scheme and WORKFLOW transition POST function associations for the event.

The events are classified in two a System event (JIRA defined events) and Custom event (User defined events). An event describes the status, the default template and the notification scheme and workflow transition post function associations for the event.

Types of Post functions carried out after TRANSITION is executed includes

• Adding a comment to an issue
• GENERATING change history for an issue
• UPDATING an issue’s FIELDS
• Generating an event to trigger email NOTIFICATIONS

Types of Post functions carried out after transition is executed includes

The Validators in JIRA checks that any INPUT MADE to the transition is valid before the transition is PERFORMED. If a validator FAILS, the issue will not PROGRESS to the destination status of the transition.

The Validators in JIRA checks that any input made to the transition is valid before the transition is performed. If a validator fails, the issue will not progress to the destination status of the transition.

Practically, it is not possible to TRANSITION an issue back to its previous status. However, you can use “onhold” feature to transition an issue back to its previous status. Here are the steps,

• In workflow, Create a global transition to the ‘On Hold’ status.
• Now from ‘On Hold’ status create another transition to every other status you want to come back to
• Since the transition NAMES cannot be the same, just add a blank space at the end of it.
• Now you don’t want the status transition from the ‘On Hold’ and ‘Done’ to ‘On Hold’ So you will hide the other status “On Hold” by ADDING the value field CONDITION on the global transition.

Practically, it is not possible to transition an issue back to its previous status. However, you can use “onhold” feature to transition an issue back to its previous status. Here are the steps,

If a WORKFLOW is active, you cannot edit the workflow name (only the description)

• You cannot delete the workflow steps
• A step associated status cannot be edited
• You cannot add any new OUTGOING transition if a step has no outgoing transitions (Global transitions are not considered).
• A step’s Step ID cannot be CHANGED.

If a workflow is active, you cannot edit the workflow name (only the description)

As such Statuses are global objects in JIRA. Changing the name of the status on ONE workflow will change the status on all workflows that use that status

• Hover over a status or transition to see the RELEVANT transition labels
• One cannot clone transitions in the workflow DESIGNER
• In the workflow designer, one cannot create annotations
• Directly you cannot set the issue.editable property.

As such Statuses are global objects in JIRA. Changing the name of the status on one workflow will change the status on all workflows that use that status

The backup data includes:

• ATTACHMENTS if SELECTED
• USERS and their group settings
• AVATARS
• Issues

The backup data includes:

In JIRA, you can TAKE backup of your JIRA cloud DATA using Backup Manager. But only one backup file is STORED at a time. The existing backup is overwritten by new ONES.

In JIRA, you can take backup of your JIRA cloud data using Backup Manager. But only one backup file is stored at a time. The existing backup is overwritten by new ones.

You can configure following things for each pair of an ISSUE type and JIRA project.

• The order of custom FIELDS appears on an issue SCREEN.
• Workflow of an issue including the statuses.
• Which custom fields and system an issue can use?
• Project accessibility.
• Permissions for what a user can do with an issue.
• Versions and COMPONENTS available for an issue.

You can configure following things for each pair of an issue type and JIRA project.

Schemes are a major part of JIRA configuration. It is a collection of configured VALUES that can be used by one or more JIRA PROJECT. For instance, Notification Schemes, Permission SCHEME, Issue Type Scheme, and so on. There are total seven TYPES of schemes.

Schemes are a major part of JIRA configuration. It is a collection of configured values that can be used by one or more JIRA project. For instance, Notification Schemes, Permission Scheme, Issue Type Scheme, and so on. There are total seven types of schemes.

Some popular add-ons for JIRA include,

• SUITES UTILITIES for JIRA
• ScriptRunner for JIRA
• Zephyr for JIRA – TEST Management
• JIRA Toolkit Plugin
• Atlassian REST API BROWSER
• Portfolio for JIRA
• JIRA Misc Workflow Extensions
• Tempo Timesheets for JIRA
• JIRA Charting Plugin

Some popular add-ons for JIRA include,

Three color will be displayed representing the amount of time spent behind the issue:

• ORIGINAL Estimate (Blue): The amount of time originally estimated to RESOLVE the issue
• REMAINING Estimate(Orange): The remaining amount of time LEFT to resolve the issue
• Time Spen or Logged (Green): The amount of time spent so far while resolving the issue

Three color will be displayed representing the amount of time spent behind the issue:

Issue change HISTORY INCLUDES :

• DELETION of a comment
• Deletion of a worklog
• Creation or deletion of an issue link
• Attachment of a FILE
• Changes to an issue FIELD

Issue change history includes :

To disable MAIL NOTIFICATION for a particular Bulk Operations, you have to de-select the “SEND Notification” CHECKBOX in the bulk operation WIZARD.

To disable mail notification for a particular Bulk Operations, you have to de-select the “Send Notification” checkbox in the bulk operation wizard.

To modify multiple bulk ISSUES, you can use Bulk CHANGE option from the “Tools” menu of the navigator. All the issues on the current page can be selected for the bulk operation.

The following LIST details the available bulk operations like:

• Workflow TRANSITION
• Delete
• Move
• Edit

To modify multiple bulk issues, you can use Bulk Change option from the “Tools” menu of the navigator. All the issues on the current page can be selected for the bulk operation.

The following list details the available bulk operations like:

You can email an issue by using the SHARE option in JIRA. You can also email other JIRA USERS a link to the issue by SHARING the issue with them or by mentioning them in an issue’s Description or COMMENT field.

You can email an issue by using the share option in JIRA. You can also email other JIRA users a link to the issue by sharing the issue with them or by mentioning them in an issue’s Description or Comment field.

JIRA’S security setting restricts the access to the issue to only those person who is allowed to work on the issue or a member of the CHOSEN security LEVEL. Security level of an issue can be set either when the issue is CREATED or when the issue is being edited

JIRA’S security setting restricts the access to the issue to only those person who is allowed to work on the issue or a member of the chosen security level. Security level of an issue can be set either when the issue is created or when the issue is being edited

The move ISSUE wizard enables you to specify ANOTHER project in your JIRA instance. Move wizard permit you to change certain attributes of an issue like

• Issue Type: If your issue is a custom issue type and does not occur in your target project, you must choose a new issue type for your issue
• Issue STATUS: If you have ASSIGNED your issue as a custom issue status and it does not exist in your project, you must select a new issue status for your issue
• Custom Fields: If you have determined required custom fields for your issue, which do not occur in the target project, you must set values for them.

The move issue wizard enables you to specify another project in your JIRA instance. Move wizard permit you to change certain attributes of an issue like

• TIME TRACKING
• ISSUE HISTORY
• COMMENTS

Cloning as issue allows you to CREATE a duplicate of the original issue so that many EMPLOYEES can work on a single issue within a single project. The clone issue can be connected to the original issue. A clone issue holds following the INFORMATION

• Summary
• Description
• Assignee
• Environment
• Priority
• Issue Type
• SECURITY
• REPORTER
• Components, etc.

Cloning as issue allows you to create a duplicate of the original issue so that many employees can work on a single issue within a single project. The clone issue can be connected to the original issue. A clone issue holds following the information

JIRA offer REPORTS that show statistics for projects, versions, people or other fields within issues. Various reports included with JIRA are

• AVERAGE Age Report
• Pie Chart Report
• RESOLUTION Time Report
• Recently Created Issues Report
• Resolved VS. Created Issues Report
• Single Level Group by Report
• Time TRACKING Report
• User Workload Report
• Workload Pie Chart Report, etc.

JIRA offer reports that show statistics for projects, versions, people or other fields within issues. Various reports included with JIRA are

• LABELLING Issue: It enables you to categorize an issue in a more informal way than assigning it to a component or version. You can then search issues ACCORDING to label.
• Linking Issue: This feature enables you to link an association between TWO issues on either on the same or DIFFERENT JIRA servers.

You can DISABLE JIRA MOBILE for the site, so that users can be unable to OPERATE the desktop VIEW of JIRA on their mobile device. JIRA mobile comes as a system add-on and can be disabled any time.

You can disable JIRA mobile for the site, so that users can be unable to operate the desktop view of JIRA on their mobile device. JIRA mobile comes as a system add-on and can be disabled any time.

Yes, it is possible to access JIRA CLOUD site via a MOBILE device. You have to just USE the URL of the JIRA cloud site in your mobile WEB BROWSER.

Yes, it is possible to access JIRA cloud site via a mobile device. You have to just use the URL of the JIRA cloud site in your mobile web browser.

The reason BEHIND using JIRA is

• Upfront and FAIR licensing POLICY
• Features that is not available elsewhere
• Get latest update on the progress of projects
• It run anywhere and RECOGNIZED with many famous companies
• EASILY extensible and customizable

The reason behind using JIRA is

It INTEGRATES with SOURCE control programs such as CVS, GIT, SUBVERSION, CLEARCASE, Visual SourceSafe, Mercurial, and Perforce.

It integrates with source control programs such as CVS, Git, Subversion, Clearcase, Visual SourceSafe, Mercurial, and Perforce.

In JIRA, an issue can be ANYTHING like a

• SOFTWARE BUG
• The PROJECT task
• A help-desk TICKET
• The leave request form

In JIRA, an issue can be anything like a

Workflow is DEFINED as a movement of the bug/issue through VARIOUS stages during its life-cycle

• Created/Open
• WIP ( Work In PROGRESS)
• Completed/Closed

Workflow is defined as a movement of the bug/issue through various stages during its life-cycle

JIRA is an issue tracking product or a software tool developed by Atlassian, COMMONLY USED for BUG tracking, PROJECT management and issue tracking; it is entirely based on this three aspects.

JIRA is an issue tracking product or a software tool developed by Atlassian, commonly used for bug tracking, project management and issue tracking; it is entirely based on this three aspects.