JIRA – Resolved by me query
Use next JQL: status was resolved by “username”
jira
Best practice of using components in jira projects [closed]
Components are like little sub-projects. Projects seem to be most useful when they group people together. I recommend to my clients that JIRA projects reflect the social organization to some degree, at least until the number of projects becomes very large. Also, avoid the use of a component named “Misc” or “Other”. They tend to … Read more
JIRA: to close or to resolve?
Typical issue workflow is the person working on the bug resolves it, and the person who opened the bug is the one who decides if the resolution is acceptable. If it is, they close it. If not, they re-open the bug for further discussion/work/wrangling. The exception to this is when a bug is a duplicate, … Read more
JIRA: Epics vs Labels vs Components
With labels and components if you want to select a group of them you need to use issue search. If you are using epics you can use issue search as well, but you also get built-in functionality in JIRA Agile. In the backlog view of a JIRA Agile board you have an Epic tab. This … Read more
Find issues that were ever assigned to me
assignee was currentUser() should do it. It will also include issues that are currently assigned to you. If it doesn’t, try: (assignee = currentUser() OR assignee was currentUser())
How to find issues that at some point has been assigned to you?
This is meanwhile possible by means of the JIRA Query Language (JQL) operator ‘WAS’, which has been introduced in JIRA 4.3 and extended in JIRA 4.4 to cover assignees and reporters as well, for example: project = “Angry Nerds” and (assignee was ‘johnsmith’ or reporter was ‘johnsmith’)