I think it's reasonable as long as we can convert everything over. Looks like issues can be imported from csv, but I don't know what happens with attachments. Would need to lookup the format requirements.
On Wed, Sep 30, 2015 at 10:38 PM, William Blevins <[email protected]> wrote: > What type of layout is this? Kanban? > > On Wed, Sep 30, 2015 at 10:34 PM, William Blevins <[email protected]> > wrote: > >> The answer to my question is that it has to be created through password >> recovery using your email. I guess the account isn't related. >> >> On Wed, Sep 30, 2015 at 10:27 PM, William Blevins <[email protected]> >> wrote: >> >>> I don't seem to be able to login with my bitbucket account. Is an >>> Atlassian Cloud account different? >>> >>> On Wed, Sep 30, 2015 at 9:58 PM, Florian Miedniak < >>> [email protected]> wrote: >>> >>>> Hi, >>>> >>>> I have created a on-demand trial setup of the JIRA + bitbucket >>>> integration here: https://scsandbox.atlassian.net with write access to >>>> both parts for Dirk, Gary, Bill Deegan and William Blevins. I'm sure >>>> there's someone I forgot ;-) Just tell me and I'll add you to the users >>>> list. >>>> The very basic integration works: >>>> - Mention a JIRA issue (SCSAND-<number>) in a commit message and push >>>> it to https://bitbucket.org/scsandbox/jira_bitbucket_integration -> >>>> The issue name will be a hyper-linked to JIRA >>>> - If you open a JIRA issue on the right there is a section >>>> "Development" which shows all commits belonging to this issue. Here you can >>>> step-wise dive into the commit until you end up on bitbucket's commit view >>>> - It is possible (but not yet configured) to modify the standard JIRA >>>> issue workflow, so an issue e.g. transits to REVIEW to FIXED when a pull >>>> request gets merged. (And there is a ton of other event/notification >>>> configuration options available ...) >>>> >>>> The trial setup is available until 2015/10/6 (due to the trial >>>> license), so feel free to check its look and feel! >>>> >>>> -Florian >>>> >>>> 2015-09-29 8:52 GMT+02:00 Florian Miedniak <[email protected]> >>>> : >>>> >>>>> >>>>> >>>>> 2015-09-28 21:42 GMT+02:00 William Blevins <[email protected]>: >>>>> >>>>>> >>>>>> >>>>>> On Mon, Sep 28, 2015 at 7:45 PM, Russel Winder <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> On Mon, 2015-09-28 at 13:56 +0100, William L Blevins wrote: >>>>>>> > […] >>>>>>> > I have used Jira and I think if we can get free instances for the >>>>>>> > project, then the direct jira -> bitbucket <- confluence setup will >>>>>>> > give us a lot of project management control. >>>>>>> >>>>>>> Personally I found Confluence a right royal pain in the arse. JIRA on >>>>>>> the other hand worked very well for me. The issue is whether SCons >>>>>>> can >>>>>>> have a JIRA directly linked to the Mercurial repository and its pull >>>>>>> requests. >>>>>>> >>>>>> >>>>>> >>>>>> Since they are all Atlassian products, I cannot imagine "no" to be >>>>>> the answer; otherwise, what is the point? >>>>>> >>>>>> >>>>> William, I agree with you, that it is not the question, *if* there is >>>>> support for connecting bitbucket hosted mercurial repos with JIRA. ( >>>>> http://blogs.atlassian.com/2012/07/connect-jira-to-your-git-or-mercurial-repositories-with-the-jira-dvcs-connector) >>>>> It's more the question how mature it is. From my previous experience, >>>>> Atlassian does a quite good job of integrating their products. >>>>> Nevertheless, the best (and IMO only) way to find out, if there are any >>>>> technical / user experiance obstacles left for using JIRA<->Bitbucket for >>>>> Scons, is to give it a try: >>>>> 1. Check for JIRA<->Mercurial on Bitbucket integration with a sandbox >>>>> project >>>>> 2. Adapt the scripts of Dirk to import the existing issues from tigris >>>>> >>>>> I'd volunteer to do this to have a solid basis for further >>>>> decision-making. >>>>> >>>>> -Florian >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Scons-dev mailing list >>>> [email protected] >>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>> >>>> >>> >> >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
