Issue #61: Taiga does not save fields unless you explicitly press the save button - fedora-change-wrangler

fedora-change-wrangler

#61 Taiga does not save fields unless you explicitly press the save button

Opened 4 years ago by bcotton. Modified 4 years ago

Looks like the value of ISSUE_CA_SUMMARY is incorrect in the production config.ini

Traceback (most recent call last):
  File "main.py", line 307, in <module>
    Change_Tool()
  File "main.py", line 47, in __init__
    getattr(self, args.command)()
  File "main.py", line 212, in announce
    climail.mails(args)
  File "/home/bcotton/devel/fedora-change-wrangler/src/mail/climail.py", line 91, in mails
    m_txt.write("== Issue Link == \n{}\n\n == Summary == \n{}\n\n== owner == \n{}\n\n== Detailed Description == \n{}".format(taiga_issue_link,cadata['attributes_values'][config['TAIGA']['ISSUE_CA_SUMMARY']], cadata['attributes_values'][config['TAIGA']['ISSUE_CA_OWNERS']], data['description']))
KeyError: '20'

Metadata Update from @bcotton:
- Assignee reset
- Issue untagged with: Taiga
- Issue tagged with: Documentation

4 years ago

bcotton commented 4 years ago

This is a documentation problem: we have to let the user know that Taiga will require each field's save button to be pressed, even if the content is empty or default.

Metadata

Assignee

None

Tags

Blocking

None

Depending on

None

Milestone

None

fedora-change-wrangler

Source Code

#61 Taiga does not save fields unless you explicitly press the save button Opened 4 years ago by bcotton. Modified 4 years ago

Close issue as:

Metadata

Documentation

#61 Taiga does not save fields unless you explicitly press the save button

Opened 4 years ago by bcotton. Modified 4 years ago