-
Suggestion
-
Resolution: Unresolved
Suggestion
Currently, the account_owner_email field is not available in Marketplace APIs or partner reports, yet it’s key to Atlassian’s customer classification. This is particularly important for partner-managed subscriptions, where the billing_contact_email might reflect the partner instead of the end customer. Access to account_owner_email would help partners better identify customers and align with Atlassian's logic. We kindly request that this field be made available through Partner APIs or reporting tools.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
[MP-369] Include Account Owner Email in Marketplace APIs or Partner Reports
| Assignee | Original: Rijoy Brahmakulam Lonappan [ 453ee4e3cd43 ] | New: Shreyash Krishna [ be598d23989a ] |
| Assignee | Original: Samridhi Tyagi [ 7591cd6f70df ] | New: Rijoy Brahmakulam Lonappan [ 453ee4e3cd43 ] |
| Description |
Original:
h3. Suggestion
Currently, the *account_owner_email* field is not available in Marketplace APIs or partner reports, yet it’s key to Atlassian’s customer classification. This is particularly important for partner-managed subscriptions, where the *billing_contact_email* might reflect the partner instead of the end customer. Access to *account_owner_email* would help partners better identify customers and align with Atlassian's logic. We kindly request that this field be made available through Partner APIs or reporting tools. h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Suggestion
Currently, the *account_owner_email* field is not available in Marketplace APIs or partner reports, yet it’s key to Atlassian’s customer classification. This is particularly important for partner-managed subscriptions, where the *billing_contact_email* might reflect the partner instead of the end customer. Access to *account_owner_email* would help partners better identify customers and align with Atlassian's logic. We kindly request that this field be made available through Partner APIs or reporting tools. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Labels | New: ecohelp |
| Summary | Original: Include Account Owner Email in Get Licences API | New: Include Account Owner Email in Marketplace APIs or Partner Reports |
| Description |
Original:
h3. Suggestion
Currently the {{account_owner_email}} field is not exposed via the Marketplace APIs or partner-facing reports. Given that this field plays a crucial role in how Atlassian determines customer classification, we believe it would be valuable for partners to have visibility into this field. This becomes especially important in cases involving partner-managed subscriptions, where the {{billing_contact_email}} may reflect the partner, not the end customer. Having access to {{account_owner_email}} would help us more accurately identify the actual customer and align our own logic with Atlassian’s. We’d appreciate it if you could consider exposing this field through the Partner APIs or associated license reporting tools. h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Suggestion
Currently, the *account_owner_email* field is not available in Marketplace APIs or partner reports, yet it’s key to Atlassian’s customer classification. This is particularly important for partner-managed subscriptions, where the *billing_contact_email* might reflect the partner instead of the end customer. Access to *account_owner_email* would help partners better identify customers and align with Atlassian's logic. We kindly request that this field be made available through Partner APIs or reporting tools. h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Summary | Original: Request to expose account_owner_email in Partner APIs to align with Atlassian's license classification | New: Include Account Owner Email in Get Licences API |