Jira - Studio Pro Connector - Changes required to make this actually usable! (Please!)

1

We caught the news announcement and were really excited about the Jira Studio Pro connector, and it has so much promise, but until these below issues are resolved, it's pretty much unusable.

 

Our New Integration Brings Together Jira and Studio Pro | Mendix

 

Issue 1) We have a Team Managed Board / Project, so it shows every single story we have, irrelevant of it being in the current sprint, and irrelevant of it's current status. So all we see is a list of the first 100 or so stories, which have all long in our projects past. So it's no use whatsoever.

 

Solution 1a) Can we make it so it only shows stories in the CURRENT ACTIVE sprint? (like it does for the other modes?). The solution of put your backlog on another board isn't a solution, as it's not just the backlog, its completed stories too that will be clogging it up. And it ruins all  our Jira data and reporting if we have to kick out any completed stories and the backlog too to different boards, not to mention the micromanging required for this. 

 

Solution 1b) Can we have FILTERS so we can only show stories that are in the status we choose? This way we can filter out all the "done", or "in progress" or "testing". 

 

 

 

-----

 

 

Issue 2) You can't change a story's status on commit.

 

Solution 2) You can change a story in the stories board before commiting, but you can't when commiting? At the point you would actually be wanting to update the status?

 

 

 

-----

 

 

Issue 3) When you setup you have to define the Project Key, and then when commit, you get to tick the issues that are relevant, this is great - but in Team Server log, it actually "doubles up" the key, making the URL link point to nothing. 

 

Solution 3: Change the URL to not be "ProjectKey-StoryKey-Number" and just be "StoryKey-Number"

 

asked 2024-09-20

1 answers