I have a project that has multiple date fields. When the screen were designed the custom dates (subscription start and end dates, first and last use dates, etc.) are placed on separate tabs. When the screen is used all the dates are moved to the right hand side of the screen under the "Dates" heading.
How do I prevent this from happening? I want to leave the screen as designed.
Thanks
Dave
Community moderators have prevented the ability to post new answers.
Thanks Jobin.
That sucks! I wonder who thought that that would be a nice feature?
Actually, me, I like it. Does the same with people.
I'd like a bit more control, but having the dates (and people) grouped together is great, and a lot of my clients are really impressed by it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think an opinion on the usefulness of a design, with the point that a lot of users find it useful is a lot more value than "that sucks".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, the ability to do this is something almost all of my clients asked for. Some are asking for more, although it's a little difficult to define a good rule for others (dates and people are very clear, but there's a lot less value in grouping text or selects by type). Conditional formatting would be really helpful as well ("if number > X, then show in red" type stuff), although I agree it should not be hard coded by Atlassian, the users need to make those decisions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nic,
I can't belive that you're still going on about this!
I'm so happy that your clients have asked for it, for mine it is a pain and a work around is required. It may even preclude Jira as a solution. If it was a choice at a project level, I would say fine, I understand.
BUT WE'RE DISCUSSING FUNCTIONALITY FORCED BY VIRTUE OF THE DATA TYPE and yes that does suck!
Kind regards
Dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We're not really discussing it. You're shouting "I don't like it". I've pointed out that a lot of people do, so there's a difference of opinion.
Your yelling about it isn't adding anything. I'd suggest you simply raise a feature request with Atlassian and see what they say. I'd definitely include mention of making it optional, because most of the people I've worked with prefer the grouping of dates together., and it would be a downgrade in most places.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nic,
You are so right, there's nothing to discuss since you have added no value to the original question. From your first post your constant whining that your clients like the functionality continues to sound like a petulant child stamping its little foot saying "I want!" desperately seeking attention.
If you think that unilaterally deciding what goes where based on data type is good design, then you sir need to go and do a computer course.
Kind regards
Dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<sigh> Insulting people doesn't add anything to a discussion either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have said that basing an activity on data type is poor design. You have also said as much. The fact that Jira’s treatment of dates suits you and some of your clients is splendid, I’m so happy for you! Would you be as happy if they decided to group all drop down boxes together irrespective of where they were placed on a screen or tab?
But then again baiting is so much more fun?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, and I've said as much in previous statements.
Is there any reason you're trying to bait me and contributing absolutely nothing of any use to this discussion any more?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well I had a similar requirement which I implemeted by providing date feilds in the edit screen , copying there value into scripted field and then showing those scripted field on to view screen.
This can solve your issue of moving the date fields on the Tab rather then on the right hand side date panel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have a similar issue. We want to position custom fields on the right. That is a similar pain and at least there is no obvious reason, why they just didn't implemented a hook for this instead of hard coding a couple of field types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know this is an old thread I've stumbled across... but does anyone else get the feeling Dave's regards might not actually be all that kind? #fakenews
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, there is no way to do that as the date fields are hard coded to be on the right side panel. You will have to modify the "view issue" bundled plugin if you want to change the behavior.
Another option will be to create a new custom field type which don't implement the "DateField" interface!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nic,
Having functionality forced by virtue of the data type, yes that does suck!
Maybe next week we can decide if a field is of a certain size or a numeric value exceeds a threshold then we can apply a colour of Atlassian's choosing?
Kind regards
Dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.