The number of votes, if not for who voted on them is a very important piece
of information. Please try to retain at least that.
Regards,
Om
On Jan 18, 2012 6:23 AM, "Peter Elst" wrote:
> > I think that NOT migrating votes and watchers would paint us a better
> > picture of what the current pri
> I think that NOT migrating votes and watchers would paint us a better
> picture of what the current priorities are from the community. I don't like
> having to lose some bugs from my watch list, but worse things could happen.
>
I agree, would it be possible to have a reply to all issues with wa
I think that NOT migrating votes and watchers would paint us a better
picture of what the current priorities are from the community. I don't like
having to lose some bugs from my watch list, but worse things could happen.
On Wed, Jan 18, 2012 at 9:30 AM, Alex Harui wrote:
> Update: In an attempt to simplify the migration of issues from Adobe JIRA
> to Apache JIRA, I am seriously considering not migrating votes and watchers...
Note that I created a "project management" component at
https://issues.apache.org/jira/b
I'd keep the watchers. If you then add the Watched Issues Gadget (
http://confluence.atlassian.com/display/JIRA044/Adding+the+Watched+Issues+Gadget
),
people will have an easier time voting again on their issues.
On Wed, Jan 18, 2012 at 9:30 AM, Alex Harui wrote:
> Update: In an attempt to simp
Update: In an attempt to simplify the migration of issues from Adobe JIRA
to Apache JIRA, I am seriously considering not migrating votes and watchers.
In addition, as I previously proposed, all bugs will be created by some
fictitious user like AdobeFlexSDK (and resolved and/or closed by the same
Alex,
I think that going forward as you stated would be ok. At this point I
think it's most important to know what the bugs are (and get issue numbers
assigned so we can manage them), then to worry about the neuances of some
of the history from the old repository.
I do think the version numbers
On Jan 13, 2012, at 12:12 PM, Alex Harui wrote:
> We’re still waiting for JIRA to get set up (and yes, we are still waiting for
> legal to clear the source code). But in investigating what it will take to
> transfer the current JIRA issues to Apache, I found this article [1].
> It talks about
We’re still waiting for JIRA to get set up (and yes, we are still waiting for
legal to clear the source code). But in investigating what it will take to
transfer the current JIRA issues to Apache, I found this article [1].
It talks about username conflicts as being a major pain. To try to reduc
