I use the search in JIRA about 50 times a day and every time it forgets what I just entered. Is there any way to tell it to remember the last search or the project code. (By project code I mean the first few letters of bug code such as "AAQT-").
That prefix is known as the project key.
(Also, what version of JIRA are you using? There are some UI differences between Cloud and most Server instances so my following advice might not make sense.)
There isn't a way to pre-define the project key in the quick search box since most JIRA instances have multiple projects, and pre-defining it for just one project doesn't make sense.
However, your browser should be able to remember previous values entered. You would have to overwrite the numerical portion that follows the key, though.
Do you mean save your search as your favourite filter? If so then you can follow these steps :
Click on "Issues" dropdown then choose "Search for issues"
Click on "New filter" button on the top-left area
Type your query
Click on "Save as" button on the above of query field
Give any search name, then it will be save under "Favourite Filters" section
Related
On JIRA tickets I can format comments entries at will : there's a toolbar with many choices for that, color, styles, underline...
But how do I get the same for description field ("descriptif" in French)?
Because what people read for explanation of a story/task/ticket, is mainly this content.
And currently the only thing we can do is to write on some descriptions "Look at comments to learn the purpose of this item/understand something" because a plain text is sometimes not enough to explain things.
This can be handled with renderers under Field Configuration Scheme.
Open Project settings -> Field Configuration.
Find the field "Descriptif"
There should be a text called "Renderers", click that. (In some version, it may be inside Edit)
Select "Wiki-style Renderer"
Click "Update" button.
And voila, it should be formatted like the Comment field.
Also, for further info you can check following Atlassian documentation.
I am working on af:query for Search functionality in ADF. The code for same is given below
<af:query id="qu1" headerText="Search" disclosed="true" styleClass="quButton" saveButtonText="Save"
value="#{bindings.SearchByTitleAndAuthor.quDescriptor}"
model="#{bindings.SearchByTitleAndAuthor.quModel}"
queryListener="#{bindings.SearchByTitleAndAuthor.processQuery}"
queryOperationListener="#{bindings.SearchByTitleAndAuthor.processQueryOperation}"/>
This provides me a Search region with various fields and 2 radio buttons named as "All" and "Any".
My requirement is that the word "Match" should come before the radio button "All". I have checked on different links that the word "Match" comes by default when we use af:query. But, its not coming in my case. Please suggest some ways in which I can get it done.
My Jdeveloper version is "Studio Edition Version 11.1.1.7.0".
Check your view object. Ensure that show match all/match any is checked as shown in the screenshot.
===EDIT===
OP was using custom skin. Causing the issue. After removing the custom skin, the issue went away as suggested.
For each model element, there is the option in EA 10 to create internal requirements, constraints and scenarios. All of them end up in reports if you use the pre-defined Basic Template.
However, if you select "structured specification" instead of the default "description" text field for a scenario, then I end up with the steps of the structured specification being ignored in the report output.
How can I have them included in reports?
It sounds like you need to create your own reporting template. This may seem a bit daunting first time out and the template editor is pretty ornery, but luckily you can use an existing template as a starting point.
Hit F8 to bring up the Generate Documentation dialog, then select the Templates tab. Click New, specify a name and select a template you like to be copied. Don't bother with a template group, and leave the fragment checkbox unchecked.
In the editor, scroll down about halfway (assuming you selected to copy the Basic template) and locate the yellow scenario > tag.
Now in the checkbox tree on the left, scroll down do Package - Element - Scenario. Note that Scenario is checked, but Structured Scenarios is not. Check it.
In the editor, note the new structured scenarios > tag. Remove the right-click-to-insert text, then right-click and select Insert Field, then State etc.
It's more than a little fiddly, but if the Basic template is good enough to begin with you should be able to add the structured scenarios with a minimum of effort.
For more information, see the help file under Reporting - RTF Documents. Note that the individual fields aren't listed in the help file, you need to open up the template editor to see what specific information you can extract to your report.
I am working on a solution to allow users to search for other users, since we use SharePoint 2010 and have access to the SharePoint people search it seems like an easy solution. For the most part it is close to what is needed but it appears to be missing a few things.
The biggest thing is the ability to search by office/location.
The search appears to return the office location but I can't seem to search on it.
I expected to be able to search on it by doing BaseOfficeLocation:"Office Location To Search For" since Department:"Department To Search for" appears to work.
I have tried Office and OfficeLocation but it just doesn't seem to work. I found a blog that said that it appeared as if this didn't work as expected but there were no more details.
Is there a setting that I need to enable or do I need to do some custom development here?
This might be a little late but here goes.
You basically need to add a metadata property that maps to the office (or whatever) field on the users profile. You then need to have that crawled. Finally you can add office to the search option. Below give you a quick overview of how to do it.
Adding a new managed metadata property
Go to Central Admin.
Go to manage service applications
Go into your search service application
On the left under "Queries and Results" go to "Managed Metadata Properties"
Click "New Managed Property"
Give it a name, I called mine "Office"
Click "add mapping" and select people
Select "People:Office(Text)" (this depends on which field on the profile you are using to put the office in)
Select "Include values from a single crawled property based on the order specified"
Click OK
Now run A FULL CRAWL. That's quite important. If it's not a full crawl it wont be picked up.
Wait for the full crawl to finish.
Adding the field to the search
You should now be able to search for Office:"office name"
That's not very useful to a user
What we want is to add it to the search options
Edit the page and go to the web part properties for the search box
Go to "Miscellaneous" and expand it
Open up "Properties" and copy out the XML. Here you now need to add in your new field.
It's going to look something like this:
<Property Name="Office" ManagedName="Office" ProfileURI="urn:schemas-microsoft-com:sharepoint:portal:profile:Office"/>
Add that in and then save it back into the web part
Click on search option, type in the office in the new office field and click search
BOOM!! Office searching.
Unless I'm missing something you're going to need to do this on both the initial people search page and the results page.
Here's a link that i based that all on.
http://blogs.technet.com/b/meamcs/archive/2010/12/23/sharepoint-2010-people-search-using-metadata.aspx
In Eclipse, there used to be a drop-down where i could click on 'past searches' so i could toggle back and forth between various search-history-results sets, is this possible in InteeliJ?
Whenever you search you have a check box of "Open in a new tab". If you do that then the results aren't overridden by a new search.
Right-click the Find view: there is an item named Recent Find Usages (You can also go to it using CTRL+E when you're in the Find view). Usually, CTRL+E is the contextual way to access history.
Please note that it doesn't save the results, but only the query. In other words, it executes the search again each time you use it.
Also note I'm using IntelliJ 10.5.2, not sure about older versions.
In the most recent versions 2019 you either need to right click on search window to get past search results or use shortcut "alt+down" to pick from dropdown list.