Comments (12)
Check this section in our FAQ and come back if that still did not solve your problem: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#7-how-to-migrate-the-work-log-time-spent-remaining-estimate-fields
from jira-azuredevops-migrator.
Do I need to shift at latest 3.0.407? right now I am at 3.0.307 @Alexander-Hjelm .
Although it doesn't working for me, I just checked my export item file, it's not even taking my timespent value.
{ "source": "timespent$Rendered", "target": "Microsoft.VSTS.Scheduling.Effort", },
from jira-azuredevops-migrator.
New version does not address the effort fields. ^^
Maybe try to migrate the field to a custom integer field for the purpose of testing?
I don't know if maybe the VSTS fields could have automation behind them or not.
Here is a config sample that has worked for me before:
{
"source": "timespent$Rendered",
"target": "Custom.TimeSpentHours"
},
{
"source": "timespent",
"target": "Custom.TimeSpentSeconds"
},
from jira-azuredevops-migrator.
Maybe the MapRemainingWork mapper could help you as well:
{
"source": "timeestimate",
"target": "Microsoft.VSTS.Scheduling.RemainingWork",
"mapper": "MapRemainingWork",
"for": "Bug,Task"
},
I don't think the tool can convert hours to minutes as of today, because only seconds and hours is available in jira. If a field has decimal value for the number of hours, then the same value will be migrated to ADO.
from jira-azuredevops-migrator.
Thanks for response this does work for me but let's say I've one task which have time spent 25.666666667 then It's showing 25.6666667 in my effort field in ADO, is there any way that I use so I get round figure value or 25.7 something because 25.66666667 is very weird to show. @Alexander-Hjelm
from jira-azuredevops-migrator.
Not to my knowledge, at the moment. We would need to update the MapRemainingWork mapper, or write a new mapper entirely.
One workaround could be to write an automation in powershell that accomplishes the same thing between your export and import steps.
from jira-azuredevops-migrator.
Ok, and I noticed one thing that my history which in Jira work item which isn't fully showing in my ADO work item.
from jira-azuredevops-migrator.
The usually means there is data which you have not mapped, or there were errors during the export or import and some revisions were not fully migrated. Check the log files!
from jira-azuredevops-migrator.
Thanks mate!! for help, last thing do you have any reference where I can take help from to achieve the idea you suggested about automation in powershell?
from jira-azuredevops-migrator.
OpenAI and general scripting knowledge probably ^^ I can check if we have any sample scripts that you can base your own work on. Stand by
from jira-azuredevops-migrator.
Here is a fairly undocumented python script which we have used to fix fields post-migration!
from jira-azuredevops-migrator.
Thanks Mate !!! Appreciate
from jira-azuredevops-migrator.
Related Issues (20)
- configuring "for" and "not-for" for field mapping HOT 3
- Attachments not getting rendered properly in the comments in Azure devops after migration HOT 6
- Parent - child relation - not mapped correctly HOT 10
- Custom Field in Jira not exporting the data correctly, fields missing in export HOT 26
- Link to source Ticket in Jira HOT 4
- JIra Key not found exception HOT 3
- WorkItems get repeat after importing second time HOT 2
- Update HOT 1
- Custom fields assigned a value on creation and not changed are not exported HOT 10
- why we are using revsions while migration .. instead we could have used jira api which just fetches info straightforward HOT 1
- Mapping Jira Custom Fields to Azure DevOps History HOT 11
- Import all the fields of Test case instead of few fields. HOT 1
- Is there a version of application which is supporting Jira with extension structure HOT 15
- Development / Releases are supported? HOT 6
- Jira Users are not getting migrated HOT 1
- Description Field Blank in ADO User Story HOT 3
- Flat Migration HOT 3
- Add support for development links to non-migrated GitHub repositories
- [JMOSS+JMP] Bump Newtonsoft.json + Restsharp
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jira-azuredevops-migrator.