Bug 965837
Summary: | RFE: Ability to change or update "Writer" tag after topic creation (alternate title: more accurate authorgroup). | ||
---|---|---|---|
Product: | [Community] PressGang CCMS | Reporter: | Stephen Gordon <sgordon> |
Component: | CCMS-Core | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 845415 | ||
Bug Blocks: |
Description
Stephen Gordon
2013-05-21 20:10:53 UTC
As you said the better alternative is to have the author group populated from the log details, however since there isn't any authentication this can't be relied upon atm. FWIW, heres a workaround until you can change it via a Content Spec: 1. Open the PressGang CCMS UI for the topics you want to change. 2. Select a topic and then select the "Tags" tab. 3. Remove your assigned writer tag and add the person who wrote the content. 4. Save the changes and then repeat steps 2-4 until all topics are done. (Alternatively you could use the bulk tagging to get this done as well, though I'm not sure how it works anymore, so you may not be able to remove your assigned writer tag) I had a look at this, this afternoon and I'll have to talk to the team about what syntax/functionality to use when adding/removing a Writer. The main reason is the global writer parameter is set to the user who creates the Content Spec and that means that all topics in the content spec will be given that writer tag. So perhaps what we need is something like: Overwrite (or add if none are set): "Writer = lnewson" Remove: "Writer = -lnewson" Add: "Writer = +lnewson" (The above is very similar to the way normal tags are handled) With the above "Overwrite" wouldn't work via inheritance though, due to the issue I initially mentioned, but the others would be inherited. Example spec: Title = My Book ... [Writer = lnewson] Chapter: Introduction [Writer = +sgordon] Some Topic [3737] Another Topic [123] ... Chapter: Middle Content New Topic [N, Concept] ... Chapter: Conclusion Some Topic that needs to be reassigned [456, Writer = sgordon] So in the above the first two topics would get "sgordon" added as the assigned writer, along with the original writer. The new topic would have "lnewson" as the assigned writer and the last topic would remove any current assigned writers and set it to "sgordon". The overwrite mechanism I'm a bit unsure atm though, due to how easy it would be to remove all the writers un-intentionally, so perhaps it's better left just for new topics. |