atlas-create-jira-plugin-module builds module creates broken module (depency injection not working)

Description

To reproduce:
Install the Atlassian SDK
(https://sdkrepo.atlassian.com/deb-archive/atlassian-plugin-sdk_6.2.2_all.deb)

  • run atlas-create-jira-plugin

cd bugged-modules

pick (for example) 4 custom field

  • atlas-run

  • go to local jira instance

  • login admin:admin

  • go to issues -> custom fields

  • add custom field
    -see log for depency injection failure

The log suggeste adding a component-import, but that doesnt resolve the problem (it does show a extra module in the add-on view in JIRA, but still fails to inject)

Environment

None

Testing Notes

None

Activity

Show:
Joseph Harris
March 27, 2018, 11:31 PM

** How do you know you didn't make it worse? [(i)|https://aqg--app.ap-southeast-2.dev.public.atl-paas.net/info?id=existingFeatureHaveNotMadeItWorse\|https://aqg--app.ap-southeast-2.dev.public.atl-paas.net/info?id=existingFeatureHaveNotMadeItWorse%5D]
*** Does it affect issue card? [(i)|https://aqg--app.ap-southeast-2.dev.public.atl-paas.net/info?id=jswIssueCard\|https://aqg--app.ap-southeast-2.dev.public.atl-paas.net/info?id=jswIssueCard%5D]
**** Check card issue layout on plan mode and work mode
**** Check Subtask and Epic (Shown as card or panel), configure issue type
**** Card layout, days in column, card color configuration, set resolution
**** Check Card shown on Gadget, Wallboard, cards printing
**** Check Keyboard shortcuts
**** Check Right click menu: Flag, comment, move to backlog (top/down)
**** Check Card operations: Drag/Drop issues, transition to column with multiple status, ADV edit and auto refresh
**** Check Verify on mobile/tablet view. And also check if it effects on JIRA Mobile product
**** Check Common frontend risk: Performance, Cross browser testing, Responsive

Nathan Neulinger
March 22, 2016, 12:24 PM

FYI, related to this bug - there is a similar issue in the module creation for a post function (33). It's putting this in the factory:

public MyPostFunctionFactory(WorkflowManager workflowManager) {
this.workflowManager = workflowManager;
}

which triggers a complaint about the workflowManager bean dependency. Removing that from the constructor entirely and just using ComponentAccessor seems to resolve the issue.

Internal support issue: GHS-36771

Fixed

Assignee

Joseph Harris

Reporter

Oswaldo Hernandez

Add-on Type

None

Team

None

CC

None

Risk factor

None

QA Kickoff Status

None

QA Demo Status

None

Story point estimate

None

Story Points

5

Sprint

None

Fix versions

Priority

Minor