nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Due" field present on dates section, not in screen configuration.

Robert Anthony_h2lqyo

Ok this ones weird.

I have a project connected to an external piece of software, but I'm not sure if its relevant.

I have multiple date fields on this projects screen config, but on some tickets, a "Due" field appears with a prepopulated date. It's not the "Due Date" field and there is no custom field in the system called Due, so I feel like it's being triggered by same kind of calculation of the other date fields. The weirder thing is, there is no "Due" field on this project/issue types Screen Scheme. The field is not referenced at all in the history/activity section of the affected tickets. I'm leaning towards this has something to do with the external system it's connected to, but has anyone else ever seen this?

Accepted answers

All comments

Iago Docando

duedate is a sytem field, not a custom field.

It is called DUEDATE in the database but maybe in Jira you're seeing a translation (in spanish I can do a JQL search by "duedate < startOfDay(+7)" but it shows in the screen as "A entregar: dd/mmm/yy" and if I have to search the field within the field configuration schema I must search "Fecha de entrega").

Hopefully this can point you in the right direction. Best of luck and let me know if anything happens

Robert Anthony_h2lqyo

Thank you for the response, but it doesnt seem to be the due date field, and the due date field is not on the screen configuration. Just called "Due"

Iago Docando

I still think that's the system duedate, based only on your description. You said:

a "Due" field appears with a prepopulated date.

This is exactly the behaviour I described with my jira in spanish ("a entregar" translates to "due"), the name showed in the screen is not exactly the name of the field. It is a bit confusing, fully agreed.

there is no custom field in the system called Due

Well... pretty much self explanatory. If something can be either A or B and you know for sure that it ain't B... then it can only be A.

In any case, you should use the "Where is my field?" tool and search for "due date" (the system field I mean, just to be clear). The tool will tell you if the field is indeed present in the screen or if it doesn't otherwise. Check this from different screens (create, edit, view). There's not much you can do to identify a field.

And as a general rule of thumb, it is a terrible practice to have any number of custom fields with the same name (or so similar that you could ask yourself "why do I need two different fields for this?")... much worst (in my opinion) with the same name that an already existing system field. All this confussion could have been easily avoided just by not having a bunch of fields with a very similar name.

I hope you can sort things out. If you find new leads come back at me with them but with the information at hand at the moment... that's my best guess.

Iago Docando

Also... there's one way to know for certain instead of going with "it doesn't seem to be the due date field":

Create a new issue. Update the DUEDATE value directly in your DataBase. Then come to jira to check if the value you updated is the value showed in screen.

Robert Anthony_h2lqyo

bump

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server