Comments
-
An approach we take is by using the script runner, a custom field and a transition. The recipe is as follows: * Add a new 'version picker' custom field and call it 'add version' * Add a circular global transition and call it 'add version', the transition has one transition screen containing the 'add version' custom field.…
-
Do you have setup project 1 such that only human1,2 and 3 can access it ?
-
Hi Piotr, There are indeed different solutions on the marketplace - check following query https://marketplace.atlassian.com/search?q=issue+synchronisation 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 your use…
-
Connections of the newrelic agent are outward (ie from JIRA towards the newrelic site). Also the instrumentation added in the jsp's are contacting the newrelic servers (and not the way around). I'm also pretty impressed with it.
-
So, Suppose you have 2 confluence instances, both connecting through crowd, one licensed for 500 users, the next to 2000 users. How do you set up the global permissions such that we don't need to upgrade our 500 user license to 2000 ? Francis
-
I would create a transition allowing to set the 'actors' and validate in the transition that both fields have been provided and that these are different.
-
Hi Jana, This is certainly possible - check the [col.xyz.defaultSort|https://wiki.idalko.com/display/TGPD/col.xyz.defaultSort] property. When this property is set, the grid is sorted on this specific column (either ascending or descending) When multiple columns are specifying a defaultSort, the sort order is according to…
-
How do you combine this with version management ?
-
Nope - this is related to the integration between the two plugins. Apparently the IssueHtmlView is returning null in your case, which it shouldn't. Trying to understand the circumstances when this happens is subject of the support request which we track in our jira.You don't need to use the groovy script approach.
-
Hmm - your ticket on our system was marked as resolved.Due to some quirck, your reply on our request for feedback went unnoticedIt's now back on our radar with an elevated prioritySorry about that, thanks for elevating it.Francis
-
It is being handled as a support case, we will report back here once issue is fixed.
-
Just forward the case to support.tge@idalko.com, which will create an account and raise a ticket.
-
Can you forward this case to support.tge at idalko.com ? This will create an issue on our JIRA and an account for you. IssueHtmlView should not return a null.Once fixed we can report back in this channel.Francis
-
For the xporter people - what is com.xpandit.jiraxporter.utils.FieldMapper.formatCustomField doing ?
-
scripted custom fields :-) That sounds as a neat idea - looking forward to give it a go.
-
Hi Jamie, It's through fisheye. How would you do it if you have subversion plugin installed ? Francis
-
Thanks for this Andreas.
-
I just installed the SEO manager from Play SQL https://marketplace.atlassian.com/plugins/com.playsql.seo-manager/server/overview Nicely done.
-
You might consider to synchronize both JIRA's such that you can raise in your JIRA and resolve it in the next. There are a couple of synchronization add-ons available on the marketplace. https://marketplace.atlassian.com/search?q=issue+sync If you would consider to roll out such a solution, please consider exalate also…
-
Hi Jeremy, Atlassian answers is a nice demo environment for Questions. We're using it quite a bit during demo, as it contains a huge amount of questions and answers. Any chance that this will be kept alive ? Francis
-
Did you consider a scripted field (script runner) which is set with the total size of all attachments related to an issue ?
-
ok - thanks, will try this out.
-
Check out following document https://confluence.atlassian.com/display/SDKB/How+to+configure+notifications+for+breached+SLAs We have a filter with following jql "Time to first response" < 2h OR "Time waiting for support" < 4h and the support team is subscribed on that filter. Check out…
-
Looking at the marketplace there are multiple solutions https://marketplace.atlassian.com/search?q=issue+sync Thanks anyway Francis
-
Hi Flavio, Did you find a solution for the database synchronisation ? Francis
-
Hi Kalpana, There are different solutions to synchronize JIRA issues with QC Defects. We are the team behind Exalate (which is one of these commercial solutions). It allows to synchronise HPQC Defects with JIRA issues bidirectionally. For more information - check out * http://www.exalate.com * https://docs.exalate.com *…
-
Did you consider the SQL plugin for confluence. It allows you to query the jira db directly, not really the jira issues macro but a valid alternative imo.
-
Found https://jira.atlassian.com/browse/JRA-24515It is not supported.
-
Abdoulaye, I'm missing the point. The link you provided, presents the stash command line.
-
I thought so, but you never know. If they have $$$, they would spend it on stash - jira - confluence, but that's not the case. Thanks