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

Manual linking annotation not working #91

Open
edmorley opened this issue Aug 5, 2020 · 2 comments
Open

Manual linking annotation not working #91

edmorley opened this issue Aug 5, 2020 · 2 comments

Comments

@edmorley
Copy link
Member

edmorley commented Aug 5, 2020

Hi

In heroku/heroku-buildpack-python#1006 I added the annotation @W-7828034@ to the issue description to try and manually link it to an existing work item.

However no comment was left of the issue from Git2Gus saying the work item has been linked. In addition no labels were added.

Looking at the implementation here:

await addLabels({
req,
labels: [sails.config.ghLabels.userStoryLabel]
});
}
return await createComment({
req,
body: `This issue has been linked to a new work item: ${getWorkItemUrl(
item,
hideWorkItemUrl
)}`
});

...it seems that Git2Gus tries to add labels before adding the comment, and that it uses the built-in label names and not the custom labels specified by issueTypeLabels (though I guess we'd need a reverse map due to one to many).

For this repository the default labels don't exist, so my thought was that the label addition was failing thus preventing Git2Gus from reaching the comment-adding stage.

However even after I manually created the USER STORY label (needed due to #88), and then removed and re-added the @W-7828034@ annotation, Git2Gus still isn't linking the items.

I don't suppose there are any errors in the Git2Gus logs that can shed light on this? :-)

@jag-j
Copy link
Collaborator

jag-j commented Aug 5, 2020

@edmorley - Thanks for this issue and all the other ones you have logged. Very helpful! We are aware of most of them, but it is nice to have them in writing here. I'll be taking care of them during my next PTOn (likely end of 228). I'll keep you posted. Thanks!

@edmorley
Copy link
Member Author

edmorley commented Aug 6, 2020

@jag-sfdc awesome, thank you :-)

edmorley added a commit to heroku/heroku-buildpack-python that referenced this issue Jan 29, 2021
Since the Git2GUS tool has a number of bugs/deficiencies which mean it's
not usable for the time being. If that changes in the future we can add
this configuration back and re-evaluate.

For example:
- forcedotcom/git2gus#97
- forcedotcom/git2gus#90
- forcedotcom/git2gus#91
- forcedotcom/git2gus#92
- forcedotcom/git2gus#86
- forcedotcom/git2gus#15

Closes W-8825462.

[skip changelog]
edmorley added a commit to heroku/heroku-buildpack-python that referenced this issue Jan 30, 2021
Since the Git2GUS tool has a number of bugs/deficiencies which mean it's
not usable for the time being. If that changes in the future we can add
this configuration back and re-evaluate.

For example:
- forcedotcom/git2gus#97
- forcedotcom/git2gus#90
- forcedotcom/git2gus#91
- forcedotcom/git2gus#92
- forcedotcom/git2gus#86
- forcedotcom/git2gus#15

Closes W-8825462.

[skip changelog]
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