Fragments have a binding variable "jiraHelper", which you'll see when you hit 'Help' in the fragment editor.
Which goes to: https://docs.atlassian.com/software/jira/docs/api/9.12.8/com/atlassian/jira/plugin/webfragment/model/JiraHelper.html
From the javadoc, you can debug the available/known values inside the condition, like this:
log.warn("== debug start ==")
log.warn("request uri: " + jiraHelper.getRequest().getRequestURI())
def params = jiraHelper.getRequest().getParameterMap()
params.entrySet().forEach((entry) -> {
log.warn("debug entry.. " + entry.getKey() + ":" + entry.getValue())
})
log.warn("== debug end ==")
Which results in log containing this:
== debug start ==
request uri: /secure/Dashboard.jspa
debug entry.. selectPageId:[23100]
== debug end =
Therefore you might conclude that the following would work in your case:
String requestUri = jiraHelper.getRequest().getRequestURI()
String dashboardId = jiraHelper.getRequest().getParameter("selectPageId")
if (requestUri.endsWith("Dashboard.jspa") && "20310".equals(dashboardId)) {
return false // because fragments, false should mean.. hide? I think
}
return true // either not a dashboard, or no id in params, so display the button
That said, your use case is rather.. peculiar? And also, if the dashboard is your "default" dashboard, it won't include the ID in url. I.e. opening just dashboard with no ID will show you the first one off the list, which might be the one you are trying to detect, but you couldn't in this case.
I really do not like fragments and they will run on basically every page visit so you can expect a tiny tiny performance hit when each page request has to go through this filter. (Which I mean, it's 1 or few milliseconds at best, but still).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.