Not able to configure Github for Jira

[MASUM]

i have installed Github For Jira app from app list 
and when i click on Get Started it takes a long loading time and then fails with a message 

---

Something's gone wrong

Our team has been notified. If the problem persists, please contact Atlassian Support.

Reload page

---

[Ollie Guan · Accepted solution]

Hi @Scott Porter,

Here are some of my suggestions for reference

First, the standard of deliverables has been reached. It should be considered that the sprint has been completed, then we can end the current iteration in Jira.

Second, the sprint that has ended is not easily tracked in the Scrum Board. It is recommended that you create Kanban for the version to manage these backlogs that have completed the sprint, and perform the release operation on the version after the project is launched.

[Scott Porter]

Thanks @Ollie Guan!  So, we've set this up and I think this is exactly right in principle, but we're having some trouble in practice. we created a new Kanban board for Implementations.  we want to put those issues that have been completed in the sprint (Done) and ok for implementation onto that Kanban board until they are released.

When an issue is marked as "Done" in the sprint (which it correctly is, it has been accepted and is complete in the sprint) how do we get it to show up on that Implementation Kanban?  How is this part done;

"It is recommended that you create Kanban for the version to manage these backlogs" and "perform the release operation on the version after the project is launched"

That's the part we're struggling with.  Thanks again for your help! 

@Carr Oduro 

[Ollie Guan]

My pleasure^_^

[Scott Porter]

So what do you think about how to get the Done issues on to the Kanban? Is there a good way to do it? 

[Ollie Guan]

I wonder if I understand it correctly?

When an issue is marked as "Done" in the sprint, do you want this issue to appear automatically on the Kanban Board?

Matching of the Kanban board's column and the Issue state should be able to achieve the above functions.

[Scott Porter]

Ha, ok. Doesn’t have to be automatic, in fact some done issues will not go to that board. It’s like this: 

issue is in the sprint and marked Done. At the end of the sprint, some -not all- of the issues will be moved to the Implementation Kanban board where they will go through the steps to be made-Ready for the next implementation to production (a release). These steps (tasks) May include training, documentation, special notices, etc and will occur at various stages in the Kanban (Ready, in progress, training, done). At the end of the Kanban they are done-Done and in production. Hope that makes sense. :) 

[Scott Porter]

HI @Ollie Guan thoughts on this one?  What we need is to have an item "Done" in the active sprint, so that it's counted as done - but then moved to another Kanban board where it will live until it is put into production, which may be at some time in the future (several sprints from now).  Thanks for your ideas on this one! SP

[Ollie Guan]

Hi @Scott Porter,

Can you take a screenshot to show the matching relationship between the status and columns of the two boards you currently have? 

[Scott Porter]

Hi @Ollie Guan I think we've figured this out.  Created new "Done"status' and new board filters to get these to show up. Thanks for your help!  

[erick.coimbra]

I posted it as an answer- not sure if you would receive a notification if commented here. 

[erick.coimbra]

@Scott Porter You could have also created a filter choosing DONE issues withing a specific time period specified by you OR used some kind of labels system for the filter e.g DONE issue with a label like 'GoProduction'or something.