You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it workable to import issues from {other thing x} but specify --only-after to filter what the importer would try to import?
My use-case:
I want to try out Linear. I want to try it out with data from my existing issue tracker (github). The one-time import is fine for me to get started and evaluate with.
I expect to spend some days
configuring it
confirming it meets the requirements different stakeholders have (we have a long spreadsheet!)
opening up the trial to other users (both day-to-day hands-on engineering types and leadership types) and then showing them how to get their needs met (or finding out x isn't possible, or needs more thought)
As soon as I open up the trial group to more people, we're now split-brain between linear and current tracker. Some people will need to look in both places. I'd like to minimise the time we need to be split-brain.
(It's hard to get people to try out a second thing (as in "hey, please try out this potential replacement to our workflow [which means duplicating effort between 2 systems]") while it's not certain that it'll get adopted - more so than a "hey, try out this totally new addition to our workflow".)
So, periodically during the trial I'd like to import things that have been happening over in github issues, so that the linear-tryer-outers need do less.
I don't mean sync - that comes with lots of fiddly bits that I bet wouldn't be worthwhile to support. I just mean "go import the issues that were created after x [last time I did an import]".
Is this something that is workable?
I think my alternative is to drop/recreate everything inside linear reasonably regularly during the trial, or at least once at the cut-over point.
The text was updated successfully, but these errors were encountered:
Hi there
Is it workable to import issues from {other thing x} but specify
--only-after
to filter what the importer would try to import?My use-case:
I want to try out Linear. I want to try it out with data from my existing issue tracker (github). The one-time import is fine for me to get started and evaluate with.
I expect to spend some days
As soon as I open up the trial group to more people, we're now split-brain between linear and current tracker. Some people will need to look in both places. I'd like to minimise the time we need to be split-brain.
(It's hard to get people to try out a second thing (as in "hey, please try out this potential replacement to our workflow [which means duplicating effort between 2 systems]") while it's not certain that it'll get adopted - more so than a "hey, try out this totally new addition to our workflow".)
So, periodically during the trial I'd like to import things that have been happening over in github issues, so that the linear-tryer-outers need do less.
I don't mean sync - that comes with lots of fiddly bits that I bet wouldn't be worthwhile to support. I just mean "go import the issues that were created after x [last time I did an import]".
Is this something that is workable?
I think my alternative is to drop/recreate everything inside linear reasonably regularly during the trial, or at least once at the cut-over point.
The text was updated successfully, but these errors were encountered: