January 24, 2025 - Import and Integrate Backlog Refinement

Hi groupimport and integrate, here are your backlog refinement issues for January 24, 2025.

Engineers

Reply to each top-level comment with your refinements, using this template:

[...Explanation of your estimate, thoughts, or considerations...]

- **Weight**: ...
- **Issue / MR breakdown**:

• Remember to keep any clarifying discussion in the issues themselves.
• Remember to be careful what you discuss here about confidential issues.

When you have refined all of the issues then unassign yourself.

Engineering Manager

When this issue is due, for each issue that was refined:

• Assign a weight.
• Remove the ready for next refinement label.
• Add the workflowready for development label.

Click to see a template to use.

Issue was refined in <link to this issue>.

/weight <weight>
/unlabel ~"ready for next refinement"
/label ~"workflow::ready for development"

You can then close this issue.

Issues

1. Direct Transfer - check batch export status before enqueueing PipelineBatchWorker
2. Re-classify bulk_imports as gitlab_main_cell with an appropriate sharding key and investigate if other tables have not been classified correctly
3. Project Export - PG::QueryCanceled: ERROR: canceling statement due to statement timeout
4. User Contribution Mapping - Add API support for CSV reassignments
5. Direct Transfer - Contributions of ghost user should be directly assigned to ghost user on destination

changed due date to January 31, 2025

added devopsmanage groupimport and integrate meta sectiondev typeignore labels

assigned to @georgekoltsov, @wortschi, @.luke, @justin_ho, @rodrigo.tomonari, @carlad-gl, @jnutt, @SamWord, @obaiye, and @knejad

Direct Transfer - check batch export status before enqueueing PipelineBatchWorker #430325 backend

Weight 2, MR 1

Re-classify bulk_imports as gitlab_main_cell with an appropriate sharding key and investigate if other tables have not been classified correctly #499829 backend database

There's a few pieces to this, but I'll guess-weigh:

• Weight: 4
• Issue / MR breakdown: ~2 MRs

There's an open discussion on the issue, I went ahead and added a weight already - @.luke @knejad please feel free to adjust once the discussion is resolved

added devopsfoundations label and removed devopsmanage label

Project Export - PG::QueryCanceled: ERROR: canceling statement due to statement timeout #504039 backend

It's difficult to estimate this issue as written because it doesn't refer to a particular error, but a class of errors. There are three specific failing queries mentioned, but they don't seem to be an exhaustive list, it's not guaranteed that the same fix would apply in all cases.

• Weight: 2 per MR
• Issue / MR breakdown: 3+ MRs

Agree with James that it's difficult to estimate this. Part of the task is investigative, and it may be that index creation isn't the fix. Perhaps as guess weight (mostly for investigation + some kind of appropriate action whether it's fix or further issues):

• Weight: 3
• Issue / MR breakdown: 1

User Contribution Mapping - Add API support for CSV reassignments #513794 backend

There's only a small amount of controller logic in the current implementation. The heavy lifting is done within services which would be easy to connect to new API endpoints.

!160748 (diffs)

So, I think:

• Weight: 2
• Issue / MR breakdown: 1 issue, 1 MR (or 2 MRs if the one implementing it would prefer to do a separate MR for download vs. upload.

Notes:

• #513794 is blocked until the above MR is merged.
• Adding an API endpoint for the upload would likely include duplicating the workhorse changes made in the previously linked MR.

Direct Transfer - Contributions of ghost user should be directly assigned to ghost user on destination #514014 backend

Weight 2 - 3 days, 1 MR

unassigned @justin_ho

unassigned @.luke

unassigned @jnutt

unassigned @obaiye

closed