Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Type: Epic automation setup request #100

Closed
brentc opened this issue Feb 2, 2023 · 18 comments
Closed

Type: Epic automation setup request #100

brentc opened this issue Feb 2, 2023 · 18 comments

Comments

@brentc
Copy link

brentc commented Feb 2, 2023

From

Team: Mobile Developer Experience

To

MDX

@brentc
Copy link
Author

brentc commented Feb 2, 2023

We've mostly moved over to GitHub for project planning. This is so we can sync our GH project plan tasks with Jira for Eng reporting.

@chadwhitacre
Copy link
Member

Our first in sentry, let's do it! Here's a PR to add the label, I'm seeing a perms issue in Unito so I'll need to resolve that as well.

missing perms

@chadwhitacre
Copy link
Member

PR landed, need to resolve perms issue.

@chadwhitacre
Copy link
Member

I pinged IT about it.

@chadwhitacre
Copy link
Member

I filed a ticket.

@chadwhitacre
Copy link
Member

Resolved! The MDE project in Jira had had "Adminstrators" removed from it, only Global Admins could modify.

@chadwhitacre
Copy link
Member

chadwhitacre commented Feb 3, 2023

Okay @brentc this is ready. Can you test it out by labeling an issue in the sentry repo with both Type: Epic and Team: Mobile Developer Experience? The expected result is a synced epic issue created in the MDX Jira board that also shows up on Releases.

@brentc
Copy link
Author

brentc commented Feb 3, 2023

Resolved! The MDE project in Jira had had "Adminstrators" removed from it, only Global Admins could modify.

Ah, my bad. I only created the project this week, and guess I didn't get the permissions right.

@brentc
Copy link
Author

brentc commented Feb 3, 2023

I added the Type: Epic label to getsentry/sentry#43833.

Not seeing anything happen yet....

@brentc
Copy link
Author

brentc commented Feb 3, 2023

Also some how getsentry/sentry#43973 and getsentry/sentry#42044 got added to the Jira MDX project

@chadwhitacre
Copy link
Member

Sigh. Sorry for the mix-up. Turns out it's seemingly not possible to match on the presence of two labels, I didn't notice until now that the condition for the team label is "is not." 🙄

is not

I'll work with Zac to move those errant epics to the right project.

@chadwhitacre
Copy link
Member

Okay phew it's a multiselect. :]

phew

Seeing getsentry/sentry#43833 synced! We good?

@brentc
Copy link
Author

brentc commented Feb 3, 2023

Looks like it! 🎉

@brentc brentc closed this as completed Feb 3, 2023
@brentc brentc reopened this Feb 10, 2023
@brentc
Copy link
Author

brentc commented Feb 10, 2023

Had to reopen because I didn't setup the original project properly (that's why the permissions were weird when you looked into it).

The new MDX project is this one: https://getsentry.atlassian.net/jira/software/c/projects/MDX/boards/190

@brentc
Copy link
Author

brentc commented Feb 13, 2023

@chadwhitacre while you weren't looking, I broke the syncing badly.

Every newly sync'd MDX Epic goes to the FEEDBACK board (as a task) 😢

@chadwhitacre
Copy link
Member

Hey right so this is a mess, it turns out that these are OR'd not AND'd. 😭 😩 😖

OR

This means that all of the flows I thought were separate are in fact in a race condition to "capture" GitHub issues as they're created with the Type: Epic label, regardless of the project.

disabled

At this point I'm bailing on the automation, I had hoped to put something together quickly that helps us out but it's been two weeks and despite working with Unito support this is not converging on a workable solution. Sorry, gonna have to drop back to manual creation/linking. I've disabled all of the automations, I'll update docs soon and also try to clean everything up here asap. :(

@chadwhitacre
Copy link
Member

Closing this and will track overall switch to manual in #106.

Sorry @brentc. 😞

@brentc
Copy link
Author

brentc commented Feb 13, 2023

Ah, too bad. If you need any help with future attempts to get things working, let me know! Happy to try all sorts of things to get something working here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants