francis Atlassian Partner

Hi Jamie, Yes the plugins are enabled. I found some references where plugins who instantantiate a customfieldmanager statically got into troubles. Francis

The question is - How do you do this from the rapid board, such that the backlog is displaying the issues of your query, without the need to reconfigure the rapid board filter ...

Hello Eda, We created the pivot gadget exactly for this purpose https://marketplace.atlassian.com/plugins/com.idalko.pivotgadget/server/overview Have a look and let us know if this is matching Francis

Access to transientvars would fix this issue. https://jamieechlin.atlassian.net/browse/GRV-449 Francis

Jamie, How do you get the comment of the last transition - if any. lastComment is set, even if the transition didn't have any comment, so containing a comment which is not relevant to the transition. Francis

Aha - now I understand. Not sure who I should attribute the answer. Arthur answer is correct, but Akassab's answer more clear... F.

Hi Arthur, This is what we tried, but once that you start a sprint, the next sprint cannot be started. Also sprints are defined in a specific project. I have been looking for more information on this topic (what is a sprint entity in greenhopper and how can are issues linked into a sprint) but I didn't find a good…

Hi Akash, There are various synchronization solutions available on the marketplace - check following query https://marketplace.atlassian.com/search?q=issue+sync We are the team behind Exalate (which is one of these solutions) https://marketplace.atlassian.com/plugins/com.exalate.jiranode/server/overview It fully covers…

(shameless plug) Check out the pivot table addon. It allows to create these types of overview https://wiki.idalko.com/display/PTGD/Example+with+issue+count+by+issue+type%2C+status+and+resolution The pivot gadget can be installed from the marketplace https://marketplace.atlassian.com/plugins/com.idalko.pivotgadget

You might hit a known issue, which forced us to use post-it notes again https://jira.atlassian.com/browse/JSW-13530 Atlassian scheduled a fix for JIRA 7.2.7 If it is, vote for it Francis

Hi Thomas, The subject of the log statements is harmless - when accessing a grid table, hibernate does a couple of checks like 'is the index available'. The way it does this check is by trying to create it, which results in this error. Still the logging is troubling quite a bit of users, so I created a bug to be resolved…

Hello Ernie, we have the same issue. Did you find/developped a solution ?

Hi there, This is not yet available, but we are currently developping it as a public api (with a REST and Java version) Details can be found here https://wiki.idalko.com/x/J4NsAg Planning - first need to get tge compatible with JIRA 7, api is next on the backlog Francis

The page moved to another location in the mean time ... thanks for mentioning it.http://www.idalko.com/display/IW/Separation+of+specifications+and+tasks

You can use the create and link new issue to split off a development task from a customer issue, and automate the interaction between the two using some groovy scripts (check the script runner plugin), in such way that if the development issue reaches a completion state, the customer issue is automatically progressed to…

Just a small note, which I forgot to mention. Next to the database connection, you should also specify the tablename using the property gd.tablename = somename For instance gd.columns = id, sku, product, unit, pricegd.tablename = lineitemsgd.ds = jira col.id = ...

Jig, (The evaluation version is functionally identical to the paid for add-on) The default configuration has been setup such that it doesn't store grid modifications in a database. The message you see is a warning that when you restart JIRA, this data will be lost. (we thought it would be nice to provide such warning) The…

Yes that works, but I was hoping that there would exist something like summary equals "the quick brown fox jumps over a lazy dog" Thanks anyway, Francis

Hi Toni, I know this is an old post - things evolved quite a bit since 2014. There are currently different solutions on the marketplace for cross instance issue synchronisation - check following query https://marketplace.atlassian.com/search?q=issue+synchronisation We are the team behind Exalate (which is one of these…

Björn, There are many options and next to the ones that Benjamin promoted, you should also have a look at Exalate. This product has been designed exactly with your use case in mind. Francis

We would love to have a tempo report based on epics. Until now, we are using the account feature of tempo. Configuring it is straightforward, but it requires an admin to do it. https://tempoplugin.jira.com/wiki/display/TEMPO/Account+Manager

I'm always using the java provided interfaces as documented here http://docs.atlassian.com/jira/latest/com/atlassian/jira/issue/Issue.html Also, the existing .vm templates are a tremendous source of inspiration :-) To access the name of the issuetype use something like $issue.getIssueTypeObject().getName() Francis

yes, you can Actually the word file is generated using a velocity template which can be found under .../atlassian-jira/WEB-INF/classes/templates/plugins/issueviews/single-word.vm Note that the vm file needs to be adapted again when you upgrade jira. You might also look at other solutions (like generating a report using…

Correct - I did make a mistake in the column query. The first attribute in the query is interpreted is the label showed in the select list, the second is the value. Both (label and value) are stored in the grid table. So you are right col.projectItem.query = select pkey + ' - ' + summary, id from jiraissue where project =…

Hi David, This is certainly possible using a column query in your grid table definition. Your grid configuration would be something like ################### Grid properties#gd.columns = projectItem, dataPoint1, dataPoint2gd.tablename = projectItemsgd.ds = jira################### Define the projectItem column as a list…

What should the effect be when running the SQL, I assume the query will only bring up one entry? Both entries in the search result have the same page id...

ck, The answer is that you can't remove it from the screen, unless that you remove it from the field configuration. So - no there is no solution (without modifying .vm files) Francis

Well, let's lift the curtain a little bit more. The reason why these users don't want to see the resolution field is because they are tracking the outcome of an issue using the status of the issue. ie. they have a status 'rejected' and 'fixed' ... The fact of tracking outcome in the status field is historic, and well…

Hi Nick, It might not be what most users want, but these users are asking for it, so at least I can tell them how to implement it if at all possible. But thanks anyway for confirming what I suspected. Francis

Right. For the reason why - the use case is similar to a 'known issues setup' where you just want to show the summary, the description and a couple of custom fields, but not the other fields, while these fields are still relevant for the management of the issues. Should the fact that the resolution field is showing, even…