As part of our new project we are trying to build a report using tableau.The report presents the information for a sprint as per the requirement.Currently we are manually updating the data source for the report.
"Is there a way through which i can access the JIRA information for a sprint and store it in a database so that i can abolish the manual updates".
Yes, due to Jira's popularity there is a Jira API for the vast majority of programming languages with which you could accomplish this.
I personally would suggest the jira-python api due to it's vast documentation that can be found here: https://jira.readthedocs.io/en/master/api.html#jira.
Then you would simply call sprints(...) or sprints_by_name(...), and iterate through the results printing relevant information into your database.
Related
I am writing a Java command like program to fetch Scrum information using Jira Rest API. I am not seeing any restful api to find a given completed sprint Committed and Delivered Story points or velocity chart information.
Can anyone help me out with what service I have to call to get it ?
I am using a raw rest call using basic authentication.
Unfortunately the answer varies for the Jira installation type
Jira Cloud
There's no direct way to get data about a sprint through the api, but I believe POST /rest/api/3/expression/eval would be your best option. From there you could find all the issues from your intended sprint with a JQL like Sprint=4, and then tally the story points. It's not perfect, but the best I'm aware of.
Jira Server/Data Center
Based on your version you may have to take the same approach as for Cloud, however some older versions of Jira have the Agile API which would probably speed things along
I'm using the Rally SDK 2 to manipulate user stories from Javascript in a "Custom HTML" application.
I can query a story and retrieve its attributes.
I can update some of the attributes, like the Name of the Iteration for instance.
How can I add a successor to my story?
If I understand well, I should edit the "/HierarchicalRequirement/.../Successors" of my story, but I don't understand how to do that.
Would someone have an example, please?
Unfortunately, I don't have an exact example you can use, but the successors (or predecessors) are 'collections'. As such, you need to 'add' to the collection. There is an explanation of some of this here: https://docs.ca.com/ca-agile-central/saas/apps/2.1/doc/#!/guide/collections_in_v2
Built into the model for the artefact are routines to handle all the details. If you want more details, then you can download the sdk-debug.js file from the Rally server. To get to it, open up the developer tools in your browser and have a look where a custom app would get the sdk.js file from. The debug variant is formatted for humans to read and a very useful source of how to do things at the low levels. The definition of Rally.data.wsapi.ModelFactory has some good tips.
One of the recommendations I make to people starting out writing custom apps, is to use the developer tools in the browser to watch the network traffic that the Rally UI makes - and then work backwards to code.
Is there a native JQL (not a plugin) that returns tickets that have linked issues listed as "is blocked by" (so I can see all my blocked tickets).
All I have found is linkedIssues() but that can require a specific issue ID to search for which is entirely unhelpful.
I am using Jira Cloud 7.4.
In the core JIRA JQL functionality the closest thing you have, as you've already found out, is linkedIssues() that requires a parent Issue reference.
What you need is Adaptavist ScriptRunner, they have a function called hasLinks(). There are also a handful of other add-ons that offer this functionality but like ScriptRunner, they all cost money.
Related JIRA community question
JIRA Cloud feature request
The below query is also helpful (add it in the filter setup):
project = "Project ID" AND issuetype in (story, Spike) AND Sprint = "Sprint ID" AND linkedIssue in issueHistory()
According to Esther Strom's answer on this Atlassian site, there's a new query type:
Atlassian has very recently introduced a new JQL function called issueLinkType, which can be used in filters, but also in boards.
It's not perfect; if you're already using card colors for something else, you won't be able to use this as well. It also behaves inconsistently when a ticket has links of multiple types. But if you're looking for an easy way to get a view into what might be blocked, and what might have blockers, it works pretty well.
In KQL you can specified the type of link.
For what you want to do here what you can use
issue in linkedIssues([Issue#],"is blocked by")
I would like to analyze the search terms submitted by our JIRA users so we can formalize best practices for creating subjects and descriptions.
I'd like to avoid having to pull the search terms out of log files, where I believe they live if the right log levels are set.
I am familiar with jira-python and server-side JIRA customization, but this one's stumping me.
Is there a programmatic way to generate a list of the search terms submitted to JIRA? (Client-side/API is ideal, but server-side is okay too.)
Appreciate any advice folks can share, pointers to references, and so forth!
There is no API for this, but you can get this information from the webserver logs or by looking at saved_searches directly in the database. Clearly these would be only the saved filters, not all queries performed.
What about catching everything that is submitted to search field (client-side) and log it on server side (POST to servlet).
I want to know how many people have visited a particular isssue in order to know its popularity( I can't trust on number of watchers of the issue) .Is there any way (JiraDB or anything) by which i can know how many people(just the count) have visited any particular issue.
The question can be modified like this : Top 10 mostly visited issues in a week or so.
Seb's earlier answer provides a possible solution for JIRA Cloud. I am not aware of any off-the-shelf product for behind-the-firewall installations of JIRA, and I do not believe that views are tracked anywhere in the JIRA database.
For behind-the-firewall instances, you could certainly write a script to parse the JIRA access logs (stored in $JIRA_HOME/logs/access_log*) to count issue accesses that way.
The JIRA access logs are stored in a format that is similar to the Apache access log format, so you just need to parse out accesses to individual issues by looking for URLs of the format "http://MYJIRA/browse/ABC-123".
Out of the box this is not possible. Jira does not log view counts for single issues.
You could have a look if there is any plugin for this at https://marketplace.atlassian.com/search?application=jira
E.g. https://marketplace.atlassian.com/plugins/communardo.connect.usage.statistic.addon looks like it could fit your requirements, but I personally have never heard of it.