original ticket was assigned to [email protected] Now, I am logging in as [email protected]. Because, [email protected] with the password on https://malhar.atlassian.net does not work on new JIRA on https://issues.apache.org/jira/browse/APEXMALHAR.
~ Yogi On 5 January 2016 at 11:10, Thomas Weise <[email protected]> wrote: > Is it possible that you are logged in as a different user? > > > On Mon, Jan 4, 2016 at 9:30 PM, Yogi Devendra < > [email protected]> > wrote: > > > No. I am not able to see 'start-progress' button. > > > > I have commented on INFRA jira ticket with the screenshot. > > > > ~ Yogi > > > > On 5 January 2016 at 10:45, Thomas Weise <[email protected]> wrote: > > > > > You are in the committer role and should be able to do this. Do you see > > the > > > "Start Progress" button? > > > > > > Please log the issue here: > > > > > > https://issues.apache.org/jira/browse/INFRA-10144 > > > > > > > > > On Mon, Jan 4, 2016 at 9:06 PM, Yogi Devendra <[email protected] > > > > > wrote: > > > > > > > Hi, > > > > > > > > I am working on this ticket: > > > > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-1958 > > > > > > > > But, I am not able to move it from 'open' to 'in-progress'. > > > > Also, not able to add work log. > > > > > > > > Is anyone else facing similar issue after migration of Malhar JIRA? > > > > Any suggestions for this? > > > > > > > > ~ Yogi > > > > > > > > > > > > ~ Yogi > > > > > > > > On 3 January 2016 at 15:18, Thomas Weise <[email protected]> > > wrote: > > > > > > > > > The JIRA migration for Malhar is complete: > > > > > > > > > > https://issues.apache.org/jira/browse/APEXMALHAR > > > > > > > > > > The old instance is readonly. > > > > > > > > > > Thomas > > > > > > > > > > > > > > > On Fri, Dec 11, 2015 at 10:35 AM, Thomas Weise < > > [email protected] > > > > > > > > > wrote: > > > > > > > > > > > It is tracked here: > > > https://issues.apache.org/jira/browse/INFRA-10144 > > > > > > > > > > > > > > > > > > On Fri, Dec 11, 2015 at 10:15 AM, David Yan < > [email protected] > > > > > > > > wrote: > > > > > > > > > > > >> There is a slight problem. The previously resolved JIRAs are > > > > > "unresolved". > > > > > >> Example: > > > > > >> > > > > > >> https://issues.apache.org/jira/browse/APEXCORE-24 vs > > > > > >> https://malhar.atlassian.net/browse/APEX-24 > > > > > >> > > > > > >> APEXCORE-24 has Status: resolved, Resolution: unresolved. > > > > > >> APEX-24 has Status: resolved, Resolution: fixed. > > > > > >> > > > > > >> As a result, common filters in APEXCORE that only list > unresolved > > > > > tickets > > > > > >> are now listing previously resolved tickets. > > > > > >> > > > > > >> David > > > > > >> > > > > > >> On Mon, Dec 7, 2015 at 8:40 AM, Thomas Weise < > > > [email protected]> > > > > > >> wrote: > > > > > >> > > > > > >> > Should work, but now it will be APEXCORE-123 instead of > APEX-123 > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > On Mon, Dec 7, 2015 at 8:14 AM, Siyuan Hua < > > > [email protected]> > > > > > >> wrote: > > > > > >> > > > > > > >> > > Can we use same git commit message to resolve/comment on the > > > issue > > > > > >> > > > > > > > >> > > On Sun, Dec 6, 2015 at 2:07 PM, Thomas Weise < > > > > > [email protected]> > > > > > >> > > wrote: > > > > > >> > > > > > > > >> > > > Please start using the ASF JIRA for core: > > > > > >> > > > > > > > > >> > > > https://issues.apache.org/jira/browse/APEXCORE/ > > > > > >> > > > > > > > > >> > > > You may have to create a login is you have not already > done > > > so. > > > > If > > > > > >> you > > > > > >> > > have > > > > > >> > > > access related problems, contact me. > > > > > >> > > > > > > > > >> > > > There were a few issues with the migration, including > > > > fixedVersion > > > > > >> and > > > > > >> > > > resolution fields. Those should be fixed soon and don't > > affect > > > > > work > > > > > >> > with > > > > > >> > > > current issues. All migrated issues have a link to the old > > > JIRA > > > > > >> added. > > > > > >> > > > > > > > > >> > > > Malhar will move work will start once the migration > process > > it > > > > > >> tuned. > > > > > >> > > Until > > > > > >> > > > then continue to use the old JIRA instance (for Malhar > > only): > > > > > >> > > > > > > > > >> > > > https://malhar.atlassian.net/projects/MLHR/issues/ > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > Thomas > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > On Sat, Dec 5, 2015 at 12:49 AM, Amol Kekre < > > > > [email protected] > > > > > > > > > > > >> > > wrote: > > > > > >> > > > > > > > > >> > > > > Great news. Nice > > > > > >> > > > > > > > > > >> > > > > Thks > > > > > >> > > > > Amol > > > > > >> > > > > > > > > > >> > > > > On Fri, Dec 4, 2015 at 3:22 PM, Thomas Weise < > > > > > >> [email protected] > > > > > >> > > > > > > > >> > > > > wrote: > > > > > >> > > > > > > > > > >> > > > > > Gavin from the infrastructure group is going to > migrate > > > the > > > > > Apex > > > > > >> > core > > > > > >> > > > > JIRA > > > > > >> > > > > > to ASF this weekend. We will make it readonly now and > > send > > > > an > > > > > >> > update > > > > > >> > > > when > > > > > >> > > > > > the new instance is ready. > > > > > >> > > > > > > > > > > >> > > > > > Thanks, > > > > > >> > > > > > Thomas > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > >
