Explore topic-wise InterviewSolutions in .

This can be confirmed through the entries in the audit logs. And this happens because that field is missing on APPROPRIATE edit or CREATE screen of your project. Go to SCREENS page and enable that field. ADDITIONALLY, you should check the permissions of the account under which you are running your AUTOMATIONS.

4 ACTIONS are supported by the JIRA ADVANCED fields:

1. Clone issue
2. Create issue
3. Edit Issue
4. Transition Issue

These actions are found in More Options. And they are useful if we want to update system or CUSTOM fields for which we don’t have a NICE form control. It is important to specify a JSON object in VALID REST API

This happens when the custom FIELD “XXXX” is not configured properly i.e. ENABLED in the system or not configured. You can solve this problem by ensuring that the custom field is present in the destination PROJECT ALSO and the supported values are present in them.

The BEST solution is to reference objects USING names instead of ID. If this cannot be done then, we have to make the IDs same across environments. This can be achieved by following these STEPS:

1. CHANGE the DEV environment as per your need and IDs
2. Finalize the script
3. Use project configurator and transfer these changes to PROD
4. Copy PROD DB to DEV

Health CHECK is an important WAY to find the proper FUNCTIONING of our instance. This can be done by:

1. Going to “GENERAL Configuration”
2. Clicking on “Troubleshooting and support tools”
3. Clicking on “Instance Health”

“Time TRACKING” and “ALLOW unassigned issued” are two important settings in Global settings that MUST be exactly similar between both importer and EXPORTER instances of JIRA for this to work PROPERLY.

• Duplicate names of same type is not supported; with DIFFERENT type it is supported
• Image files such as ICONS are not supported
• Avatars of PROJECTS or users is not supported
• If any PLUGIN is referred but not installed or enabled, then it will not be supported
• Notification templates are not exported or imported
• It does not support any other languages apart from English

The best WAY to HANDLE these without changing the schema is to fill some dummy values in those orphan fields then IMPORT it. Then export immediately so that new layout is received then import again.

This way it WORKS.

JIRA automatically creates entries for it in all existing field configurations. Also, when a new field configuration is created it is created with entries for all fields existing in the INSTANCE, EITHER system or custom. 

This means that it is never necessary to create an entry for a field in a field configuration, as they exist from the moment either a custom field or a field configuration are created. 

Project Configurator takes this fact into account, and if it detects a situation where it would have to create an entry for a field in a field configuration considers it an anomaly and stops the IMPORT with that message.

The solution is:

1. Maybe the referred custom field is a locked field which must be created by a plugin/application such as JIRA Agile/Software. In this case, ensure the right version of the plugin/application is installed at the target instance.
2. Verify also that it is installed with the same locale it had been installed at the source instance. The ultimate goal is that the set of JIRA Agile/Software custom fields is exactly the same in both instances.
3. If the field had to be created when the configuration is imported, verify that the import of custom fields was not disabled
4. If it is a time tracking field, CHECK that time tracking is ENABLED in the target instance. Otherwise, the time tracking fields are not available.

 The most common errors are related:

1. EMAIL address where they are not in correct format
2. Custom fields USING disabled plugins
3. Mandatory or required fields were blank
4. Invalid references to objects in workflows that can occur due to DELETION of those customizations
5. Name mismatch due to extra SPACE, comma or underscore

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

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

Components are sub-sections of a project; they are used to GROUP ISSUES WITHIN a project into smaller parts. Components add some structures to the projects, breaking it up into features, teams, modules, subprojects and more. Using components, you can generate reports, collect statistics, and display it on dashboards and so on. 

To add new components, as shown in the above screen you can add name, DESCRIPTION, component LEAD and default assignee. 

POP and IMAP or MESSAGES to some EXTERNAL SERVICE

In the form of JIRA ISSUES, an issue COLLECTOR allows you to gather feedback on any website. In administration if you click on Issue collectors an option will open asking Add Issue Collector. Once you have configured the LOOK and FEEL of an Issue Collector, embed the generated JavaScript in any website for feedback

• You can have as many sub-task as NEEDED under an Issue 
• You cannot have a sub-task for a sub-task 
• Once a sub-task is created under a parent, parent cannot be CONVERTED into a sub-task 
• A sub-task can however be converted into a parent issue 
• You can work on your sub-task WITHOUT having NAVIGATING AWAY from the parent issue 

 It will display the active sprint information. All the ISSUES or users’ stories will be DISPLAYED into three categories as SHOWN in the screenshot below To do, In Progress and Done to show the progress of the PROJECT or issues.

Plan mode displays all the user stories created for the PROJECT. You can use the left-hand side menu to decide the basis on which the issues need to be displayed. While on the right-hand side menu CLICKING on the ISSUE, you can create subtasks, LOG WORK etc.

It integrates with source CONTROL PROGRAMS such as CVS, GIT, Subversion, CLEARCASE, Visual SourceSafe, Mercurial, and Perforce.

• On the 'Components' SCREEN, FLOAT over the significant Component to show the Delete option. 
• You will be PROVOKED to connect these issues with another Component on the off chance that you wish

• Your client presents a demand to your service agents through an entryway or by means of email. 
• An service desk sees the demand in their JIRA Service Desk line and INVESTIGATES the issue. 
• Your client and different MEMBERS utilize the entry or email to talk about the demand with your service desk agent, who WORKS in Jira Service Desk. 
• Your specialist finishes the demand and your client is fulfilled!

YES, Jira provides backup FUNCTIONALITY of data. But it can save backup file only once and next time when you backup, the EXISTING data will be OVERWRITTEN

Set of instructions GIVEN as CONFIGURATION to Jira to define a FIELD’s BEHAVIOR LIKE necessity of fields, field visibility, etc.

Issue TRACKING is made EASY with three different COLORS representing three different STATUS of an issue.

• Blue color - Estimated TIME to resolve issue
• Orange color - Remaining time to resolve issue
• Green color - Total time spent (Logged In) to resolve the issue

A FEEDBACK FORM PROVIDED to collect issues or bugs in the WEBSITE that are to be addressed by the customers of the website is one of the FEATURES provided by Jira. And to address bugs, users no need to have Jira registration.

Jira software comes in THREE different DEPLOYMENT OPTIONS including cloud, server and DATA center OPTION.

Zephyr for JIRA (SERVER and Center versions) is a NATIVE application that exists in JIRA and brings TEST management capabilities to any JIRA project

You can ADD gadgets to your own personal dashboard(s). To add a GADGET to the default dashboard for your JIRA application, you must be a JIRA admin.

• Some APPLICATIONS ALLOW dashboards that are shared by groups of people. If you have permission to update a shared dashboard, the other people SHARING the dashboard will see your changes, too.
• Go to the dashboard by selecting the Dashboard link in the header.
• On the dashboard, Click Add Gadget.
• Use the gadget wizard to choose the gadgets you want to add. You can see a list of these gadgets in Gadgets for JIRA applications.

Project shortcuts can be added to your project navigation page to any online RESOURCES your team may want to ACCESS. These shortcut links are AVAILABLE to EVERYONE who has access to the project

FOCUSING your query so it pulls the right AMOUNT of data, so the user sees only the INFORMATION relevant to the CURRENT item at HAND

• Go to GENERAL configuration
• Click MANAGE add ons
• Go to system
• Locate the CONFLUENCE MOBILE plugin
• Expand and disable it

YES

Voting on an issue is a feature in JIRA that allows PEOPLE to go to view issue PAGE and vote their OPINION on if the issue is resolved or not.

This feature is NOT available by default and needs to be enabled by Admin.

Yes; it will RETURN test projects where ASSIGNEE is same as CURRENT user

lastLogin()

By adding ~ in BEGINNING of word. For example: ~NAME will SEARCH for data that ENDS in “name”

PROJECT NAME and Project KEY

USE DOUBLE quotes.
For example, JIRA will treat the following CSV as a single RECORD: Summary, DESCRIPTION, Status, "Login issue", "This is on a new line", Open

This will SHOW you all the tickets assigned to MEMBERS of a TEAM, so you can see how MUCH work they have on their plates.

During import operation, the configuration file is used for mapping of COLUMNS of CSV with columns of JIRA DB. We have an option to USE the EXISTING CONFIG file or new one.

It includes a set of FUNCTIONS that query around MANY of JIRA’s core CONSTRUCTS: users, versions, issues, COMMENTS, etc. It is a plug in.

• Project = Pipeline And status CHANGED FROM “INPROGRESS” to “Completed” BY “J.Smith”
• If the ID is jsmith and not J.Smith then we don’t NEED “” [double QUOTES]

YES

• (status=resolved AND project=SysAdmin) OR assignee=bobsmith?

NOTE that if you do not USE PARENTHESES, the STATEMENT will be EVALUATED left-to-right

You can use parentheses to ENFORCE the PRECEDENCE of the Boolean OPERATORS in your QUERY, i.e.

(status=resolved AND project=SysAdmin) OR assignee=bobsmith

YES, but we will NEED plug in CALLED as “search ATTACHMENTS”

GenericEntityException: ERROR importing data: java.lang.Exception:

com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while

inserting: [GenericEntity:Action][id,31274][body......SQL Exception while executing the following:INSERT INTO

public.jiraaction (ID, , issueid, AUTHOR, actiontype, actionlevel, rolelevel, actionbody, CREATED,

UPDATEAUTHOR, UPDATED, actionnum) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (ERROR: invalid byte sequence

for encoding "UTF8": 0x00)

The import process to POSTGRESQL is trying to interpret plain-text comments as UTF-8 characters

and will END up with the above errors because of the NULL values in the data.

Solution is to unzip the FILE and remove null characters or use utility like XMLCleaner to remove

such NULL Characters.