You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the feature you have in mind and explain what the current shortcomings are?
We can now view the Publishing report tab, which includes logs for each plugin. This feature is useful for exchanging failed publishes via JSON files. We receive these reports from clients daily, but they often lack Creator context, which is crucial as it significantly impacts the publishing process.
How would you imagine the implementation of the feature?
It would be great to have a Creator report log, similar to the Publish log report.
Are there any labels you wish to add?
I have added the relevant labels to the enhancement request.
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered:
It would be great to have a Creator report log, similar to the Publish log report
I just want to add that this should be part of the "Publish report" so that if your publish succeeded, someone shares their logs that it includes the Creator context and the plug-in logs of that too.
As in, it should not be a completely isolated report.
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
We can now view the Publishing report tab, which includes logs for each plugin. This feature is useful for exchanging failed publishes via JSON files. We receive these reports from clients daily, but they often lack Creator context, which is crucial as it significantly impacts the publishing process.
How would you imagine the implementation of the feature?
It would be great to have a Creator report log, similar to the Publish log report.
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: