Github Tracker Issue Creation button and Associated Github Tracking Link field for Applications

[leogopal]

Components / Tools

A dynamic Github issue creation button to replace the bookmarklet for application tracking.

Description

I am a current team rep for the Community Team which does the event applications for meetups and WordCamps.

We use Github which we recently adopted after seeing the success in the trainnig team especially for attribution to the contributors profile.

➡️ I need a small feature added, and was wondering what would be the process of getting this done.

Currently, I have created a Bookmarklet much like PressThis which grabs the data from the Edit screen of an application and prefills a github issue with the right labels, and content for easier adding and tracking (and attribution).

The bookmarketlet is literally just a github URL which extracts data into URL parameters in order to achieve this.

What problems did you encounter (rationale), and what do you propose to solve/improve/enhance them?

The problem is having to have all those working on applications to learn how to install the Bookmarklet and maintaining it for various browsers, plus not being able to know whether there is a linked Github Tracker Issue created.

If we can have a button that does the same as the bookmarklet below the status box on the right, that doest the same thing, plus the ability to add the link to the tracker of the Github Issue they just created - so we can associate them.

What opportunities do you see (rationale), and what do you propose to achieve them?

This would highly help contributors see which applications are unclaimed and untracked and getting to change them inside the editor screen themselves without having to undo or add the bookmarklet.

Screenshots / Screencasts

Proposed Solution for Meta/Central:

Stakeholders

EVERYONE will benefit as this will streamline and make visible all things, around applications, this helps make contribution easier.

Facilitator, Community team, XXX Community, Event Organizers, etc.

How does this new feature contribute to the goals

** Remove the need for the the bookmarklet. A Native option will help improve the process and flow and improve contributions. It removes level of entry to help with the tracker.

** Yes, this is something that is definitely needed, espcially as not as many or some of helping

Can it truly achieve your desired outcomes?
This is simple and all I really need.

You may have already considered various other options and made assessments. Please briefly explain.

Acceptance Criteria

For example:

1. Implement dymanic github tracker creation button on the Application edit screen

• The button should dynamically contain the following values:

• The Event Type

• The Event Title

• The Event Central Edit URL

• The Current Event Status

And push through to Github like so

• Once the link is clicked, and the Tracker issue created, the user should then be able to full in the tracker link into the Central Edit Screen of the application as per the previous example screenshot.

Priority

Pretty High, as this is a blocker for many non-technical Event Supporters who either do not know or try to install the bookmarklet or do not keep it updated.

Reference Links:

• Link to our Tracker: https://github.com/WordPress/Community-Team
• Link to the bookmarklet: https://wordpress.github.io/Community-Team/

[pkevan]

can you link to where this wants to go, as it's not clear from the issue?

[leogopal]

@pkevan -- thanks for getting back to me - so this will only appear on the WP Admin edit screen of an application for WordCamps, Meetups, and other events:

Examples:

• https://central.wordcamp.org/wp-admin/post.php?post=8941141&action=edit
• https://central.wordcamp.org/wp-admin/post.php?post=8849362&action=edit

And I would like the button to be in the sidebar below the Status metabox.

Does that help?