Prem Chudzinski _extensi_ Atlassian Partner

We've released it Details: http://go.extensi.io/nl2/6phl/187jr.html

Hi @Kleber Fonseca, Sorry to keep you waiting but we had to refactor 80% of the code, as this feature turned to be one super complex task to integrate with Jira Software :) The good news is, we are polishing the release and we plan to ship it next Tuesday :) Cheers Przemyslaw 

https://docs.atlassian.com/jira-software/REST/latest/#agile/1.0/epic-moveIssuesToEpic ["issues": ["TEST-1"]]

import groovyx.net.http.FromServer import groovyx.net.http.HttpBuilder import io.extensi.build.rest.jira.Field import org.slf4j.Logger import org.slf4j.LoggerFactory class DetailsUpdate { static final Logger LOG = LoggerFactory.getLogger(DetailsUpdate.class) def static updateEstimate(int estimate, String issueId, int…

We'll be adding this or something similar to our plugin pretty soon. Click the Watch app link to subscribe for new release notifications.

Create a Kanban board.

same here can't use Artifact Download task

@Barry Kaplan OK we've implemented the feature now we need to name it: 1. Include epics 2. Include epics for selected version 3. Include epics' version 4. Include epics' Fix Version 5. Include epics allocated to selected version 6. Include epics using selected version What's your opinion?

Hi @Danielle (On leave until May 2025) You can filter the Epic List using our plugin There is an option "sync to issues" which will allow you to show epics related to Tasks which can be filtered using our search bar. In the next release we're adding full JQL filtering support for epics & versions lists

@osvaldo plabst there is another way

Our upcoming version will use full JQL filtering so you'll be able to do that. Drop me an email on info@extensi.io and I'll notify you once is released. PS. What do you think about the UI - any suggestions?

I think our next app release will solve your issue (original question about visible epics on the Backlog list not "marked as done") We're adding full JQL support for epic panel. You'll simply filter out all resolved epics, or find them and mark as done. Preview of upcoming feature.

As part of our plugin we display workflow statuses on the epic cards. Its easy to find Epics in Done status and mark them as Done (Epic Status Field) directly on the backlog. 

For the common backlog board for all team you can: Create My issues Quick FIlter using - JQL: assignee = currentUser() Created by me Quick Filter - JQL: creator = currentUser() That way each member will be able to see his issues. If you want to export import Quick Filters between boards you can use this tool…

https://marketplace.atlassian.com/plugins/io.extensi.jira.plugin.agileboardfilter/server/overview But server only

@fabrizio galletti The feature has been added and its called Sync to issues JQL including lock is coming next :)

Hi @Kelley Cooper, we've implemented the feature you were looking for now you can filter out stories where Team is X and see all related epics directly on the backlog more details http://go.extensi.io/nl2/6phl/18h93.html

@Sebastian Kleinholz the same goes to you ;) drop me an email

@Frank Kmiec Don't even bother with the cloud version. It's slow, limited and security may be an issue if you want to use 3rd party marketplace addons (your data processing takes place at vendor servers not at Atlassian). If you're interested I can help you choosing the right set of tools for your requirements and do the…

Due to recent Intel CPU bug they may decrease the limit :)

Hi everyone we've released sync to issue feature More details and examples here

@rsperafico I've modified the plugin itself to use PlanExecutionManager instead of NonBlockingPlanExecutionService. I just think my use case is not supported by bamboo. I'd need an API that would enforce bamboo to queue next job regardless of the concurrent build limit. My use case is pretty common. Build->Multiple…

Just tried it start doesn't work.

Hi @rsperafico, Yes that helped but that seems to be very strange behaviour. I'm looking into the plugin code and API nonBlockingPlanExecutionService.tryToStart(plan, triggeringAction);…

In the logs I can see 2018-01-03 10:15:42,761 INFO [10-BAM::PlanExec:pool-17-thread-3] [ChainExecutionManagerImpl] Build Proj-PLAN2-JOB1-66 has been dispatched Only once, and should be triggered twice.

That seems to be the solution, but now I've got a new issue with the after-deployment-trigger Here's the scenario 1. PROJ-PLAN1 2. Deployment to QA1 and QA2 3. PROJ-PLAN2 (integration tests) using After Deployment Trigger At this point I assume the QA1 and QA2 deployments should trigger Proj-PLAN2 twice. I use here…

5000 shouldn't be an issue Have a look at this video https://extensi.io/video-tutorials/agile-board-filter-jira-software/board-load-time-optimisation

@Canal OFF Admin If you're on cloud - you can't do that. If you're on server - you can use our app - Agile Board FIlter You'll be able to configure default searchbar fields to show component dropdown as default field https://extensi.atlassian.net/wiki/spaces/ABF/pages/29948529/Customize+search+bar+fields

Yes using the Agile Board Filter app - for JIRA server only 

You can use our plugin to do that