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

Fix usage of New-JiraIssue in Jira Environment with mixed classic and "next gen" projects #337

Merged
merged 4 commits into from
Feb 18, 2019

Commits on Feb 15, 2019

  1. ** Modify ConvertTo-JiraProject to additionally store the 'style' val…

    …ue returned - for use with differentiating between classic and 'next-gen' Jira projects
    pdx-nojp committed Feb 15, 2019
    Configuration menu
    Copy the full SHA
    53476e7 View commit details
    Browse the repository at this point in the history
  2. ** Modify Get-JiraIssueCreateMetadata and New-JiraIssue to do proper …

    …error handling when the input IssueType value is not valid for the input Project value
    
    ** Modify Get-JiraIssueCreateMetadata and New-JiraIssue to use data already returned from Get-JiraProject, saving an API call and some filtering work in Get-JiraIssueType
    pdx-nojp committed Feb 15, 2019
    1 Configuration menu
    Copy the full SHA
    89e61fa View commit details
    Browse the repository at this point in the history
  3. ** Update unit tests for Get-JiraIssueCreateMetadata and New-JiraIssu…

    …e to support their usage of IssueTypes data returned from Get-JiraProject
    pdx-nojp committed Feb 15, 2019
    Configuration menu
    Copy the full SHA
    51d5d46 View commit details
    Browse the repository at this point in the history

Commits on Feb 18, 2019

  1. Configuration menu
    Copy the full SHA
    fc1c0c9 View commit details
    Browse the repository at this point in the history