I'm trying do:
project = tet1 AND issueLinkType = "is a child of"
Shows all issues that are a child but I'm trying to see how I can show only issues from a specific parent issue.
If you want to get all issues that are linked to one issue you can use the below :
issue in linkedIssues("AD-11605")
Answer was
issue in linkedIssues("MDC-27","is a parent of")
Related
I have a problem with FooterRow in Vaadin 14 and it's related to my case that I want to remove some already added FooterRows in my grid and append others but that seems doesn't work. I've tried with collection methods that getFooterRows() provide like removeAll, clear, and remove by iterating them one by one but that doesn't work. I've seen in the Github issue: https://github.com/vaadin/flow-components/issues/1538 that there is a conversation regarding it but there is not having an answer? Could someone know is there a way to do that?
Im trying to search for all the issues assigned to an user, but no results are being returned and i cant figure out why.
My JQL is the following:
project = MYPROJECT and assignee was joaoalves
In the docs it says:
The "WAS" operator is used to find issues that currently have, or previously had, the specified value for the specified field.
(Note: This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution and Status fields only.)
I have an issue assigned to the user joaoalves, but when i search with the JQL above no issues are returned.
But if run the following JQL the issue is returned:
project = MYPROJECT and assignee = joaoalves
Am i missing anything?
It works in my instance, and return issues that currently or previously assign to me. Which version of JIRA are you using?
Assignee was will return the issues which were previously assignee to tat user and current tickets which are present on that user.
Try in conjunction with the "DURING" clause and specify a timeframe. Like this -
project = MYPROJECT and assignee was joaoalves DURING ('2017-04-16 23:59', '2017-04-19 23:59')
See: https://confluence.atlassian.com/jiracore/blog/2015/07/search-jira-like-a-boss-with-jql
The was operator is looking for issues where the assignee was joaoalves but is currently not that user.
I'm trying to tidy up our Jira board and create an accurate story map.
To do that I need to come up with a query that will return open user stories within a certain project that don't have any issue links (preferably 'related to (primary)')- the last part does not seem to be supported.
I've had a look around an post of the Q&As are a few years old, so i'm wondering if it was been updated recently?
I'm using version 5.1
Thanks!
issuetype = Story and "Epic Link" != EMPTY
I used the following query:
project = PROJECTNAME AND issuetype = Story AND "Epic Link" is EMPTY
Seems to work for me, what do you guys think?
In addition to "Epic Link" = EMPTY, you might want to filter out issues that, themselves, are EPICs, since they can't have Epic Links and will otherwise show up in the search.
Here's a search to get only issues that have no Epic (but are not Epics themselves):
issuetype != Epic AND "Epic Link" is EMPTY
Just to throw another answer into the bowl.
You can use your normal workboard (Scrum, Kanban, etc) and add a swimlane with the JQL:
"Epic Link" is EMPTY
Just did this for our board after looking exactly for this.
I don't have enough points for comments or votes yet ... but to add to the one answer provided about the "Board", the JQL will work in a simple issue search as well. I just ran this JQL from Issue Search and it worked like a champ:
project = BI and "Epic Link" is empty
project = PROJECT NAME AND issuetype = ISSUETYPE AND "Epic Link" = EMPTY
How to write query that will select only issues resolved by me.
I have found some old post that says its no possible, but it might have changed.
Use next JQL:
status was resolved by "username"
In 4.4 this seems to work:
status was "Resolved" by currentUser()
More details can be found here.
The answer most often given is to use JQL for something like
status was Resolved BY currentUser()
While all fine and good, this will give you back all the issues that you have ever resolved. That is, if you resolved issue FOO-1966 and then it got reopened and someone else resolved it again it is still an issue that was resolved by you.
Here's a better way to do this in JIRA 6 and later (including JIRA onDemand).
Create a custom field called "Resolver". Make it a person field but do not add it to any forms (unless you really want to).
Edit your workflow and add a post function to the resolve issue transition in your workflow. Make the action "Update custom field" and set the Resolver to %%CURRENT_USER%%.
Publish your workflow.
Now whenever someone resolves an issue using that workflow, the Resolver field will get set to the current user. Now the Resolver field is semantically "last resolved by".
As an added bonus, you can use the value in the Resolver field to reassign issues back to the person who resolved them when they get reopened. I'll leave this as an exercise to the reader. :-)
You can use this JQL query:
"Resolved by" = currentUser()
(I just verified this in v4.1.2#531 on a standalone version)
There is also a plug in you can use in older versions:
https://studio.plugins.atlassian.com/wiki/display/JQLT/Home
None of the above worked for me on JIRA (v4.1.2#531)
However, his works:
"Resource" = currentUser() AND (status = Fixed OR status = Closed OR status = "No Change Required") ORDER BY updated
You can use the WAS operator:
JIRA - Advanced Searching : "The "WAS" operator is used to find issues that currently have, or previously had, the specified value for the specified field"
Example: status WAS "Resolved" BY currentUser()
For JIRA v6.3.4, this worked for me:
"Resolved By" = currentUser()
As far as I can tell, search for resolved by me and more generally, for status changes, is not possible until at least JIRA 4.2.1 (the version I'm using now).
Search and JQL enhancements outlined in 4.3 and 4.4 release notes look like the move in the right direction (WAS operator) but I'm not holding my breath.
None of the above solutions worked for me. I started adding a label to all my issues to resolved_by_kishore, then in advanced search, I'm using lables=resolved_by_kishore. It's working fine.
project = prohjectname AND status was "Resolved" by username and resolutiondate >= '2014/01/08'
and its variants exists in jql now
i am not sure whether they existed at the time question was asked.
i am adding this answer so that if anyone comes here can find the answer
I guess you can use this
status in (resolved) AND component = COMPONENT_NAME AND assignee in (currentUser()) AND resolved > -1d
but the new thing here resolved > -1d this to get the issues that are resolved me in this day
resourses: https://community.atlassian.com/t5/Jira-questions/JIRA-4-4-search-filter-how-to-find-issues-resolved-in-last-seven/qaq-p/77326
The values used in Status can vary (e.g. Resolved, Closed, Done, ...) so it is not reliable to use.
Instead, use resolution:
resolution changed from EMPTY by currentUser()
Using = EMPTY seems to work for searching for empty custom fields with newer versions of Jira
We have created a Custom List template programmatically using Feature.xml, Element.xml, Schema.xml AllItems.aspx, and 3 aspx forms. We have a code behind file for each of these aspx files. i.e. for the AllItems.aspx, DispForm.aspx, EditForm.aspx and NewForm.aspx.
Problematic file is AllItems.aspx. In the code behind for AllItems.aspx file we are deleting previous list items and adding new items to the list before showing them up to the user. As per expectations the code behind file for AllItems.aspx is derived from WebPartPage Class and we have tried to overload quite a few methods without much success.
Problem only occurs on the first time rendering i.e. when an instance of this list is created. When overriding OnLoad(), we get the Save conflict error, Similar is the case with OnInit(), CreateChildControls() method. However, when we override the Render() or RenderChildren() method no such error comes up but at the same time our new list items are also not visible. On browser refresh everything starts working fine as expected. It is only for the first time that the issue comes up.
What could be the possible cause for this? Any ideas, suggestions would be highly appreciated.
Best Regards,
Raghu
I had a problem with a custom EditForm.aspx. I have two lists that are linked together and a change in one causes an event handler to update the other. I have a custom control in EditForm.aspx that edits the linked list. This was causing the event handler to update the item displayed by EditForm.aspx. This in turn would cause the conflict error when the user saved the form.
I finally found that I could reset the context with:
SPContext.Current.ResetItem();
I am not sure if this will help in your case but it fixed my problem.