Friday, 17 February 2017

Explain me the difference between Issue and Risk?

Risk: A risk is something you feel may happen and for which eventuality you need to plan some mitigating actions to buy-pass it.

Issue: An issue is when a risk becomes reality and you have to drag the plan out of the drawer to deal with it.
Blogger Widgets

Explain how to create an issue in Jira via rest api?

POST to this URL
https://<JIRA_HOST>/rest/api/2/issue/

This data:
{
"fields": {
   "project":
   {
      "key": "<PROJECT_KEY>"
   },
   "summary": "REST EXAMPLE",
   "description": "Creating an issue via REST API",
   "issuetype": {
      "name": "Bug"
   }
  }
}

In received answer will be ID and key of your ISSUE:
{"id":"83336","key":"PROJECT_KEY-4","self":"https://<JIRA_HOST>/rest/api/2/issue/83336"}
Don't forget about authorization. I used HTTP-Basic one.

Click here to read original article

How to find issues that at some point has been assigned to you in JIRA?

This is meanwhile possible by means of the JIRA Query Language (JQL)

A simple query in JQL (also known as a 'clause') consists of a field, followed by an operator, followed by one or more values or functions. For example:
project = "TEST"
This query will find all issues in the "TEST" project. It uses the "project" field, the EQUALS operator, and the value "TEST".

But here you find out all issue which has been assigned to you(current user) then your query look likes below:
project = "TEST" AND assignee = currentuser()
This query will find all issues in the "TEST" project where the assignee is the currently logged in user. It uses the "project" field, the EQUALS operator, the value "TEST",the "AND" keyword and the "currentuser()" function.

Or you can use 'WAS' operator, which has been introduced in JIRA 4.3 and extended in JIRA 4.4 to cover assignees and reporters as well, for example:
project = "TEST" and (assignee was 'vikas' or reporter was 'vikas')

Explain what is JQL (JIRA Query Language)? Interview Questions

JQL stands for JIRA Query Language. It’s the most flexible way to search for issues in JIRA and is for everyone: developers, testers, project managers, and even non-technical business users. This blog is intended to be a tutorial for those who have no experience with database queries as well as those who want faster access to information in JIRA. Basically, anyone who works in JIRA can benefit from a little JQL.

If you're a technical person/developer/dba who already knows SQL, you've got a leg up because Atlassian's implementation of JQL is very similar. The search box is even equipped with code hints and inline validation to make constructing queries easy.
To try out JQL in your JIRA instance, you can:

  • Click Issues > Search for issue
  • Click Edit (If you have a search in progress)
  • Click Advanced Searching

You can then type your queries directly into JIRA. For a complete reference, check out our help docs on advanced searching. I recommend bookmarking this link – I find myself returning to it often to look up obscure queries. The docs page has a lot of content, so it's helpful to do a "Ctrl/Cmd + F" so you can jump directly to a specific topic or keyword of interest.

To know more you can read Atlassian tech blog

Find job here...