Description of problem: This file should go away and the data should be either moved to the DB or the para.json file as appropriate.
I vote for moving to the database and making it editable via the Admin UI so that editing the default bug description templates can be self-service for product owners.
(In reply to Jason McDonald from comment #1) > I vote for moving to the database and making it editable via the Admin UI so > that editing the default bug description templates can be self-service for > product owners. There is a separate bug for that specific component of config.yaml
*** Bug 1174069 has been marked as a duplicate of this bug. ***
Verified the issue. version 5.0.2.rh2 The result is FAILED. The config.yaml file still exist under data/ . The data, like doc_type_text, that you have mentioned in comment #3, should be moved to database or data/params.json, right? I can see the data items you mentioned in comment #3 still exist in data/config.yaml.
This bug will be used to eliminate the code that loads and parses config.yaml
Hi Muhammad, the last remaining blocker for this bug is Bug 1225107 which is not in this sprint. What to do?
Bug 1225107 moved to current sprint.
Tested on QA environment(5.0.3-rh4) Result: Pass