I need to move all data for one ticket from prod to test.
Is it possible to construct a query that pulls all data related to an issues provided?
Anyone every tried it? Is it even possible?
Thanks,
Easy with the REST API:
https://<jira-server>/rest/api/2/issue/<ISSUE-ID>
Related
I have a table named "User_Records" in that I have a column which is "created_by". I want to sort the records on the basis of this filter. I am very new to AWS and have looked on the internet but didn't got any solution for that. Please share your ideas as I am heavily stucked.
You could use Local Secondary Index to achieve your usecase. Please refer to the link below:
http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LSI.html#LSI.Using
Thanks,
Rohan
i try to find a way to archive project, issue and worklogs from jira to another database to increase performance.
It's someone already write a tools or have some sample of code to use to execute this goal ?
I think pass by the api will be to much expensive in ressource, so maybe i would like to pass by the database
It's there a way to transfert all old "items" who was not modified past a year ?
thanks
There is a tool I made for my needs which basically allows to convert Jira project to html website - maybe it will be useful for you: https://gitlab.com/kaszaq/jiratomkdocs/
I need to search records in JIRA by using jira key. I am able to search issues but I have to do one more task that is to find out resolved by and resolved date. I had did lots of goggling but did not find content which satisfied me.
I really appreciate to help me to solve out this problem.
Thanks,
You could do this with a calculated field using Script Runner to extract the information from the Issue History tab. Not sure how good the search is using that approach. Alternatively you can use the REST API and a script to scan issues, but that's probably too slow.
Finally I am able to solve out this problem by traversing history data. I used json call to pick history data on basis of jira key then I converted that history data into typed history collection and started looking for Resolved token. When I got Resolved token in history then I picked the assigned name. By this way I am able to solve out this problem.
Thanks for your support.
I am working on a rails application that uses sunspot solr for search. I have been asked to log (or capture in some way) each search that happens on the site; the query, the user that did the search, the result count that resulted from their search...etc, so that the company can report on what people are searching on (demand), and other things.
Before I go and make a table, that will receive an ever-growing number of rows of search data, I'm wondering if anyone has done this in a better way? Can I use analytics (google?) in some way for this? Is there some kind of service I can send this information too, such that we could easily pull reports, or create reports from?
In short, is there some better/smarter way than creating my own table and storing this all in our own DB?
I had never done this, but here are some thoughts.
If you just need to store that data I think you should do it yourself.
If you need to also provide a way to analyse the data yes, see if there is anything already done (I'm not sure but it seems google analytics only support internal search using their search bar).
If your client already have some BI tool they just need a way to access the data, and it would be easier to have it in a owned DB wich you can easily be query instead of using a provider api.
We're looking to create a tool to help with time management in Redmine. The issue we are currently having is that we want to get a list of issues that are watched by a particular user but can't find an API for it. Does anyone know if this is possible or are we just going to have to try and modify Redmine directly?
SOLUTION: Similar to the solution provided below by dmf85, I found a solution to this problem that worked for me. The Issues API takes a query_id as one of its parameters. What I ended up doing was filtering my issues by Watcher (like dmf85 said) then saving the query. I then used the query_id from that saved custom query in my API call.
At least in Redmine 3.1, there’s an undocumented parameter for the Issues API that allows you to specify a watcher directly: watcher_id. It works just like assigned_to_id, you can pass either a user ID (i.e. watcher_id=23) or the special string me (i.e. watcher_id=me).
An example of URL could be like the following: https://example.com/redmine/issues.json?watcher_id=me&key=redmine_api_key
Under your issues tab in the interface, click:
add filter
watcher
select a watcher in the box
Then, click the atom, csv, or pdf link at the bottom for a link that you can write a program to consume at your discretion.
Does this help?