After checking the Atlassian documentation about the kind of links of JIRA's issues (https://confluence.atlassian.com/display/JIRA/Linking+Issues)
I couldn't figure out the difference between: "depends on" and "precedes". Does anybody know the difference among them?
I think someone defined "precedes" locally in your JIRA instance. JIRA admins can define new link types, e.g. "Tests" with text for the incoming and outgoing links.
To answer your question, it's likely a different issue link type. How it is used depends on your local JIRA practices
Related
I was trying to find some extension (or maybe built-in functionality) for Jira which would allow to assign a status to a user like it is possible in popular messengers, e.g. "on vacation" or "doing home-office today". It would be great to see a dashboard with statuses of all users displayed together.
The only thing which sounds close to what I'm searching for is
https://confluence.atlassian.com/conf54/confluence-user-s-guide/sharing-content/user-status-updates
but that one is for Confluence and we don't use Confluence in our workflow, we have Jira and Wiki so answers like "just use Confluence" won't work.
Is there such a thing, but for Jira?
I am sorry, but : There is no such thing for JIRA (atleast for now).
Just because Atlassian provides a possibility to connect JIRA with Confluence:
https://confluence.atlassian.com/doc/integrating-jira-and-confluence-2825.html
As far as I know they have no intentions to bring Confluence type things in JIRA, but don't quote me on that.
Sorry I couldn't give a positive answer.
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.
In Jira, we use regular Web Links to point to an independent issue tracking system (for customer support). Those links can easily be identified by their domain name or URL prefix, e.g., they all have this form:
http://support.mycompany.com/ticket#1234
How can I filter for Jira issues that have links to URLs following this pattern?
The JQL editor does not offer anything related to issue links, and "link" and "URL" are genuinely bad search terms.
ScriptRunner for JIRA offers the Script JQL function "linkedIssuesOfRemote" that searches for issues that have a link to a specific web page, e.g.:
issuefunction in linkedIssuesOfRemote("http://support.mycompany.com/ticket#1234")
will return all issues that link to that page. Instead of the link you might use the link title too.
Unfortunately wildcards are not (yet) supported, thus this doesn't work:
issuefunction in linkedIssuesOfRemote("http://support.mycompany.com/ticket*")
JavaRunner for JIRA 6.28 Does have support for wild card characters so you should be able to support what you need with.
issuefunction in linkedIssuesOfRemote("http://support.mycompany.com/ticket*")