Items migrated are not retaining their Jira "state"

[meghanaik22]

Thanks a lot for sharing this tool. I was able to migrate all items with attachments and history however post migration, in TFS, all items reflect state as New (story\bug) or To-Do (task). The JiraToTFS.txt contains no errors. Impersonation setting is not set on, could that be a problem? Let me know if any further details required. Awaiting your reply.

[KilskyreMan]

Glad it was of use Meghan.

l will look into the issue you hit. To help isolate the problem did all tickets in jira come across as new (regardless of state in jira) or state settings changed in 'advanced' settings not work?

Cheers ian

Sent from Outlook Mobilehttps://aka.ms/blhgte

On Wed, Apr 6, 2016 at 12:59 AM -0700, "meghanaik22" <[email protected]mailto:[email protected]> wrote:

Thanks a lot for sharing this tool. I was able to migrate all items with attachments and history however post migration, in TFS, all items reflect state as New (story\bug) or To-Do (task). The JiraToTFS.txt contains no errors. Impersonation setting is not set on, could that be a problem? Let me know if any further details required. Awaiting your reply.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/6

If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you. We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies.

Sage Ireland, trading name of Sage Hibernia Limited. Registered in Ireland at One Central Park, Leopardstown, Dublin 18, Ireland. Registered number 300549.

Directors: L Perkins (UK) and M Parry (UK).

[meghanaik22]

Thanks for replying. All tickets were migrated fine with new state
regardless of their state in Jira, no settings were at all altered in the
Advance Settings tab.

On Sat, Apr 9, 2016 at 2:32 PM, Ian Montgomery [email protected]
wrote:

Glad it was of use Meghan.

l will look into the issue you hit. To help isolate the problem did all
tickets in jira come across as new (regardless of state in jira) or state
settings changed in 'advanced' settings not work?

Cheers ian

Sent from Outlook Mobilehttps://aka.ms/blhgte

On Wed, Apr 6, 2016 at 12:59 AM -0700, "meghanaik22" <
[email protected]:[email protected]> wrote:

Thanks a lot for sharing this tool. I was able to migrate all items with
attachments and history however post migration, in TFS, all items reflect
state as New (story\bug) or To-Do (task). The JiraToTFS.txt contains no
errors. Impersonation setting is not set on, could that be a problem? Let
me know if any further details required. Awaiting your reply.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub<
https://github.com/KilskyreMan/JiraToTfs/issues/6>

If you've received this email by mistake, we're sorry for bothering you.
It may contain information that's confidential, so please delete it without
sharing it. And if you let us know, we can try to stop it from happening
again. Thank you. We may monitor any emails sent or received by us, or on
our behalf. If we do, this will be in line with relevant law and our own
policies.

Sage Ireland, trading name of Sage Hibernia Limited. Registered in Ireland
at One Central Park, Leopardstown, Dublin 18, Ireland. Registered number
300549.

Directors: L Perkins (UK) and M Parry (UK).

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#6 (comment)

Regards,
Megha Naik.

[meghanaik22]

Hi,

Some further observations:-
1.) JIRA project following permissible states for a bug are Open, Resolved,
Closed, In-Progress, Re-Opened while those in TFS New, Done, Approved,
Committed and Removed.
2.) Current process customization in TFS does not support to add states to
a work item.
3.) Ideally there should be some mapping that would need to be done so that
a state in JIRA can correspond to which state in TFS.

On Mon, Apr 11, 2016 at 9:23 AM, Megha Naik [email protected] wrote:

Thanks for replying. All tickets were migrated fine with new state
regardless of their state in Jira, no settings were at all altered in the
Advance Settings tab.

On Sat, Apr 9, 2016 at 2:32 PM, Ian Montgomery [email protected]
wrote:

Glad it was of use Meghan.

l will look into the issue you hit. To help isolate the problem did all
tickets in jira come across as new (regardless of state in jira) or state
settings changed in 'advanced' settings not work?

Cheers ian

Sent from Outlook Mobilehttps://aka.ms/blhgte

On Wed, Apr 6, 2016 at 12:59 AM -0700, "meghanaik22" <
[email protected]:[email protected]> wrote:

Thanks a lot for sharing this tool. I was able to migrate all items with
attachments and history however post migration, in TFS, all items reflect
state as New (story\bug) or To-Do (task). The JiraToTFS.txt contains no
errors. Impersonation setting is not set on, could that be a problem? Let
me know if any further details required. Awaiting your reply.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub<
https://github.com/KilskyreMan/JiraToTfs/issues/6>

If you've received this email by mistake, we're sorry for bothering you.
It may contain information that's confidential, so please delete it without
sharing it. And if you let us know, we can try to stop it from happening
again. Thank you. We may monitor any emails sent or received by us, or on
our behalf. If we do, this will be in line with relevant law and our own
policies.

Sage Ireland, trading name of Sage Hibernia Limited. Registered in
Ireland at One Central Park, Leopardstown, Dublin 18, Ireland. Registered
number 300549.

Directors: L Perkins (UK) and M Parry (UK).

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#6 (comment)

Regards,
Megha Naik.

Regards,
Megha Naik.

[meghanaik22]

Hi,

Are you planning to provide a release soon for this issue?

On Mon, Apr 11, 2016 at 10:39 AM, Megha Naik [email protected] wrote:

Hi,

Some further observations:-
1.) JIRA project following permissible states for a bug are Open,
Resolved, Closed, In-Progress, Re-Opened while those in TFS New, Done,
Approved, Committed and Removed.
2.) Current process customization in TFS does not support to add states to
a work item.
3.) Ideally there should be some mapping that would need to be done so
that a state in JIRA can correspond to which state in TFS.

On Mon, Apr 11, 2016 at 9:23 AM, Megha Naik [email protected] wrote:

Thanks for replying. All tickets were migrated fine with new state
regardless of their state in Jira, no settings were at all altered in the
Advance Settings tab.

On Sat, Apr 9, 2016 at 2:32 PM, Ian Montgomery [email protected]
wrote:

Glad it was of use Meghan.

l will look into the issue you hit. To help isolate the problem did all
tickets in jira come across as new (regardless of state in jira) or state
settings changed in 'advanced' settings not work?

Cheers ian

Sent from Outlook Mobilehttps://aka.ms/blhgte

On Wed, Apr 6, 2016 at 12:59 AM -0700, "meghanaik22" <
[email protected]:[email protected]> wrote:

Thanks a lot for sharing this tool. I was able to migrate all items with
attachments and history however post migration, in TFS, all items reflect
state as New (story\bug) or To-Do (task). The JiraToTFS.txt contains no
errors. Impersonation setting is not set on, could that be a problem? Let
me know if any further details required. Awaiting your reply.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub<
https://github.com/KilskyreMan/JiraToTfs/issues/6>

If you've received this email by mistake, we're sorry for bothering you.
It may contain information that's confidential, so please delete it without
sharing it. And if you let us know, we can try to stop it from happening
again. Thank you. We may monitor any emails sent or received by us, or on
our behalf. If we do, this will be in line with relevant law and our own
policies.

Sage Ireland, trading name of Sage Hibernia Limited. Registered in
Ireland at One Central Park, Leopardstown, Dublin 18, Ireland. Registered
number 300549.

Directors: L Perkins (UK) and M Parry (UK).

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#6 (comment)

Regards,
Megha Naik.

Regards,
Megha Naik.

Regards,
Megha Naik.

[KilskyreMan]

Hi megahaik22

My apologies for not answering sooner. Unfortunately business commitments have kept me away from updating the tool.

Yes - I plan on looking at this issue and a couple of others that have arisen today. Hopefully I should have another release in the next two weeks.

Ian.

[meghanaik22]

OK thanks

On Fri, Apr 15, 2016 at 12:40 PM, Ian Montgomery [email protected]
wrote:

Hi megahaik22

My apologies for not answering sooner. Unfortunately business commitments
have kept me away from updating the tool.

Yes - I plan on looking at this issue and a couple of others that have
arisen today. Hopefully I should have another release in the next two weeks.

Ian.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#6 (comment)

Regards,
Megha Naik.

[meghanaik22]

Hi Ian,

I was able to migrate all tickets for more than 35 projects with their
states as New, To-Do, Done with no changes in the tool you had published. A
big thanks for your so-easy-to-use tool.

Just thought of informing, some JIRA users could not be automatically
assigned in VSTS. For some, it did work fine. Maybe you wanted to explore
further.

Thanks again!

On Mon, Apr 18, 2016 at 9:50 AM, Megha Naik [email protected] wrote:

OK thanks

On Fri, Apr 15, 2016 at 12:40 PM, Ian Montgomery <[email protected]

wrote:

Hi megahaik22

My apologies for not answering sooner. Unfortunately business commitments
have kept me away from updating the tool.

Yes - I plan on looking at this issue and a couple of others that have
arisen today. Hopefully I should have another release in the next two weeks.

Ian.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#6 (comment)

Regards,
Megha Naik.

Regards,
Megha Naik.

[tcarrol2]

@meghanaik22 I know it's been a long time, but do you remember what you had to do to migrate state correctly? Thanks!