Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intelligently translate input based on createmeta and updatemeta schemas from the jira server #15

Merged
merged 9 commits into from
Jan 22, 2024

Conversation

lhh
Copy link
Owner

@lhh lhh commented Jan 19, 2024

No description provided.

In order to avoid calling /field more than once per
session, override the field() call.  This is related
to (and arguably obviates):

pycontribs/jira#1798
Notes:
1. transmogrify_input during field update call could (should?)
   be moved to jboard.py
2. User lists require the username (name value), emailAddress does
   not work. To fix this, we need to do (1) and then issue searches
   based on assuming email addresses as user input
@lhh lhh force-pushed the devel branch 2 times, most recently from b937161 to d9f5c10 Compare January 22, 2024 15:11
Since we don't support user list manipulation by using
lists of email addresses yet, present user names instead
of email addresses (note: username _may_ also be an email
address in Jira) when rendering lists of users.

For assignee and fields that are single users, we do
support assigning by email address since we search Jira
for the username.
When you have a component or name with a comma, simply joining
the list together does not provide output you could quote and use
as input, and makes it confusing where the component name begins
and ends without looking at the component list.

So, for example, one can see:

   "component1, desc1", component2, component3

... in the output instead of:

   component1, desc1, component2, component3

... when looking at issues, in addition to:

$ jirate field TEST-1 set components '"component1, desc1", component2'
@lhh lhh merged commit 70e8a1b into master Jan 22, 2024
3 checks passed
@lhh lhh deleted the devel branch January 22, 2024 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants