I'm confused about the Search box at the top of the Backlog view. This one:
I always thought that this box searched everything - all fields. But from an accidental test - then repeated more carefully - I'm finding that it in fact only searches the issue Summary, Issue Key (and possibly some other fields).
To reproduce:
Create an issue, with summary "Green" and description "Purple".
Type "Green" in the search box: issue appears in filtered backlog.
Type "Purple" in the search box: issue doesn't appear in filtered backlog.
How can I even find out what this search box does? Or alter what it does, ideally? Because this makes avoiding duplicate issues pretty difficult.
This box is searching through Name (Summary), Code (Issue Key) and Assignee and sadly there's no customization on that as mentioned in this ticket.
Related
I have a Google Spreadsheet, used like a form, with multiple "Skills", all of which have 2 fields within them, a "required field" (used as a flag for if entry in that field is necessary) and a "Current field" (where the user provides input). I am trying to create a "Inputs Left" field which counts the number of "Required fields" which do not currently have an entry in the "Current field" across all of the fields (seen below).
To do this, I am currently using this formula (C12:P12 is the range with the values in it).
=COUNT(FILTER(C12:P12,ISODD(COLUMN(C12:P12)-COLUMN(C12)),C12:P12>0)) - COUNT(FILTER(C12:P12,ISEVEN(COLUMN(C12:P12)-COLUMN(C12)),C12:P12>=0))
The issue I am running into is when a "Skill" is not required, but a value is entered. With this formula, it counts this towards the number of inputs left, however I only want it to count towards this if it is a required field, while still allowing the user to input non-required skills (see below). In this situation, I would like to have it still show that 2 inputs a left (specifically skill 3 and 4 still need input)
I believe I could do this using a OnEdit() trigger with google scripts, but I would like to have it done using a formula if possible. I also believe I could do this with a series of normal If statements, but the actual document has many more "skills", and I believe an endless list of if statements would be hard to debug in the future. Any help is appreciated!
Ended up using a COUNTIFS statement:
=COUNTIFS(FILTER(C12:P12,ISODD(COLUMN(C12:P12)-COLUMN(C12))),">0",FILTER(C12:P12,ISEVEN(COLUMN(C12:P12)-COLUMN(C12))),"")
Because I imagine it's confusing why there is a ISEVEN(COLUMN(C12:P12)-COLUMN(C12)) (and ISODD), the reason is because I needed to do multiple of the "Inputs Left" Fields, and the "Required" field would switch between being even and odd, meaning I would need to edit the formula a lot. Using the COLUMN(C12:P12)-COLUMN(C12) normalized this, so the "Current" was always even and the "Required" was always odd.
We're using TFS for our daily team stand ups which are more task driven vs development iterations. We'd like to be able to track how many times a target date changed & in what areas that's happening the most to see if we can pinpoint bottlnecks. I'm having a heck of a time figuring out a query that will give me these results. I tried querying "History Contains Words changed target date" (based off the image you'll see in the link below) but got no results. When I just say "history contains words date", it only gives me results where someone said the word "date" in a discussion field.
Any ideas?
Screenshot of History Item
It's an expected behavior. Comments entered into the Discussion area are queryable. Change history entries, such as which fields were changed, aren't queryable.
Check the following link for more information:
https://learn.microsoft.com/en-us/vsts/boards/queries/history-and-auditing?view=vsts&tabs=browser
I have an issue which has duplicates and "duplicate by" already linked to the issue. I am trying a jql query that will list all those duplicates.
Lets say the issue ID is "10000" and the duplicate issues are "20000" and "30000". When I run the jql like this
key in (10000) AND (issue in hasLinks("duplicates") or issue in hasLinks("is duplicated by"))
I get the result set that shows me only 10000. How can I modify my jql to give me 20000 and 30000 in the result set.
You should really spend some time looking at the Advanced searching page, it has information about a lot of functionality that's hidden at first.
For your use case check this out:
JQL:
key in linkedIssues([parentIssue], "duplicates")
and
key in linkedIssues([parentIssue], "is duplicated by")`
You need to run both queries.
i'm struggling with the Ui-Grid. I am using the grouping option to group my results. This works pretty fine, but in the documentation of this feature Grouping you can find the following statement:
Optionally (and by default) grouped columns are moved to the front of the grid, which provides a more visually pleasing effect. In order to avoid creating a dependency on pinning, this is done by moving the columns themselves as part of the grouping feature, not through use of the pinning feature.
My understanding is, that it would be possible to disable this behavior. But i am not able to find how i can do so.
I want to have an action-column in the front of every entry.
Can anyone tell me how i disable the behavior that the "grouped" columns are always the first in the grid?
Thanks in advance
Found it out by myself:
You need to set the value "moveGroupColumns" to false
This value belongs to the gridOptions object
We used JIRA on-demand to manage an Agile project. Sometimes a story may be preliminarily sized in story points, but is then re-sized before commitment. I would like a query which shows the history of each story's status and point value.
For example:
Story 99 history:
1/1/2014 -- Status = Open; Points = Null
1/15/2014 -- Status = Reviewed; Points = 5
2/15/2014 -- Status = Committed; Points = 8
My goal (and maybe there is another way to do this) is to see how often we change our story sizes.
Thanks.
I thought I had a solution for you in using the "changed" JQL query (https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-WAS), but unfortunately it looks like that is not supported currently in Jira. I received the following error from our hosted Jira instance:
History searches do not support the 'Story Points' field.
So as a user on demand query I don't think it is currently possible.
The only way I see of doing this would be to have a set day/time where you would run a query to get the current story points, export it as an excel file and then do it again after you review a set of stories and write some excel functions to show the change.
The larger question would be around your agile/scrum processes as to why estimated would change so frequently as to need tracking. If the team as a whole decides the points its ok if it doesn't match the reality once we start working on it. Or is this a case where it is updated on more than one occasion before its actually being worked on? If thats the case then I'd say that the story isn't well defined and need more information before it can be estimated?
Adding to Michael's answer, the daily monitoring for a given set of results to a query can be semi-automated using a JIRA filter subscription. You will still need to extract the issues from the results manually but at least in principle you can be sure not to miss any resizing that happens.