Disclaimer: I'm not your typical Jira user. I am a sole proprietor, and I'm using Jira to track my life so that I can schedual and balance my work, errands, care-giving, fitness regimine, and most of all my full-time studies at university as a near-50 year old. Sheesh!
When I started my Jira instance it was on Server, and team vs company, and the new issue view didn't exist. Now I have a mess related to time fields that I'm trying to sort out. I'm using Company managed projects as opposed to Team managed for the greater number of configuration parameters and the road maps.
I have a Company-managed project that I use as a template to create all other projects. It has a Due Date-Time field which I need because some of my work is due mid-day.
1. In the issue view, there is a date column, but it's blank because my date fields are based on Due Date-Time, not Due Date? How do I fix that?
2. What field do I choose in my JCL filters to select by Due Date-Time instead of Date?
3. Can I move existing Date values to Due Date-Time (with a default time presumably)?
4. How can I make the Due Date-Time fields display 24H time?
Is Due Date-Time a Date-Time Picker field?
#1 I'm not sure what you're referring to. Can you provide a screen image?
#2 If you have created a custom field named "Due Date-Time" then that is the field you would select in your filters if you need to base your selection criteria on the info in that field.
#3 Theoretically, yes, you can copy data from the Due Date field to the Due Date-Time field. You should be able to create an Automation Rule for that. Refer to https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/
#4 To change the format of the field refer to
https://confluence.atlassian.com/jirakb/change-the-time-format-to-24-hours-in-jira-734234435.html
Thank you! I got #2 worked out. The following query does it : "Due Date-Time[Time stamp]" < now() AND status != Done ORDER BY cf[10900] ASC, priority DESC
I don't know why it's "Due Date-Time" for the select and cf[10900] for the where clause, and I'd swear that I did not set it up as a custom field, even though 'cf' probably stands for custom field.
#1 The Issues view is just a filter, but I don't see a way to change the columns to remove "Due" and add "Due Date-Time", as you can with custom filters.
The article you pointed me to is only valid for server installations, not cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For #4, yes, the KB was specifically for Jira Server but the steps are valid for Jira Cloud also, based on my review of my company's cloud instance. If you are finding otherwise, please provide details.
#1 Are you talking about selecting the "Issues" option from the navigation pane on the left? If so there have been a few posts on that topic in this community. One suggested changing the System Defaults columns (when building a custom filter) would change these columns, but that did not prove out when I tried it. I have not found a way to change the columns displayed when the built-in "Issues" filters are used.
#2 "Due Date-Time" is most definitely not a default field in Jira. You either created a custom field for it, or you added a third party app that added that custom field for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Trudy. When I go to Advanced Settings I see:
'jira.date.picker.' and 'jira.date.time.picker.' aren't supported in the new issue view
The new issue view formats your dates and times based on your language preferences.
So that's that.
Yes, that's the "Issues" option that I was talking about.
My guess is that it was a field from a 3rd party app. I'm glad to have it though.
I'm satisfied for now, thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh, I did not notice that caveat on the date formatting fields. Thank you for pointing that out!
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.