Hi All
Our project teams often run meeting and during those meeting jira issues are discussed and updated.
Now, we would like all absentees to directly know the changes that were made during the meeting.
Is there a way to identify the issues that were edited/created during a specific time frame say 1 hour so that absentees can know what was discussed in the meeting.?
Rahul
Labels is a far better way to do it. It also gets around the problem that Christian mentions (the "changed" operator doesn't work for all fields), and it will leave you with an easy way to refer back to meetings later if you choose informative labels. Such as meeting_dd_mm_yyyy (just remember you can't use spaces in labels)
Why dont you use another custom field. a select list or radio button. you can change the value if you discussed it during the meting. Then in JQL you can use that to filter
e.g
updated < '2013-05-23 05:00' and updated > '2013-05-23 03:00' and "Issue Discussed" = 'true'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can we use labels to tag issues discussed in CCB rather than using custom fields? Will it serve the same purpose?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes Labels also a good option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
use JQL
e.g
updated < '2013-05-23 05:00' and updated > '2013-05-23 03:00'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use a filter.
The pseudo code for it would be
project in (list of projects) and updated > (meeting start) and updated < (meeting end)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic. Thanks for your answer. However, the only loophole i can see in this query is that, issues discussed outside the meeting (i.e. any random transition by a user) will also feature in this list and will be understood as CCB agreed/discussed. How do we avoid this problem?
Rahul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic isnt't the changed function restricted to some system fields (like priority, status?).
The JIRA Misc custom fields plugin records the transition caller field if that's of any help:
https://marketplace.atlassian.com/plugins/com.innovalog.jmcf.jira-misc-custom-fields
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe off-topic but you should vote for this issue that has been around for 10 years:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use the "changed by" function, naming the attendees of the meeting.
See https://confluence.atlassian.com/display/JIRA/Advanced+Searching for other functions you might find helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Very true, but Rahul has hit upon a better option than custom fields (I was heading to labels because they're flexible, but was thinking a bit too close to the search, and Rahul beat me to it)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic and Christian for your inputs.
Rahul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.