zowe / file-transfer-app Goto Github PK

example bug report

If you are opening a file with a lot of tabs have already opened, it will be more convenient to scroll tabs to the right to show the new one

This is simply a test issue in zowe/file-transfer-app. Please ignore me.

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

Readme does not indicate how to use this desktop plugin.

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

This second test issue was produced using the github issues api via request.js. Please ignore me.

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)

We want Zowe to be an open-source project; but keeping the open-source community updated on internal progress produces hours of tedium for project managers like Nolan Rogers and Scrum Masters like Reet Chowdhary who have to fill out GitHub issues manually. This tool (eventually a bot, perhaps) will automate the process of creating GitHub issues by fetching metadata for selected Jira issues, converting them into GitHub-friendly issues, and posting them to a corresponding repo under the Zowe organization on GitHub.

MVP:
[ ] port a selected jira issue to github with a simple command-line interface. Hopefully mapping the statuses in both Jira and github
[ ] add a basic UI for usability

Nice to have:
[ ] fetch JSON directly from Jira rather than parsing XML (which requires only ordinary permissions). mroffo is waiting on RAC ticket for Jira API access

Really nice to have:
[ ] accomplish this in reverse: Issues created on a zowe github repo by open-source contributors automatically prompt Sean Grady for inclusion in Rocket's internal Jira. (likely will be a separate Issue)