OK, I made them the same order, with the addition of the Lucene Fields for
LUCENE before Environment:
Description
Labels
Attachments
Environment
On Tue, Jun 12, 2018 at 10:29 AM Cassandra Targett
wrote:
> Yeah, I wasn't sure if folks would want the labels up higher in LUCENE.
> It's easy to fi
Yeah, I wasn't sure if folks would want the labels up higher in LUCENE.
It's easy to fix though if the preference is the two forms be mostly the
same (with the exception of the "Lucene Fields").
On Tue, Jun 12, 2018 at 10:11 AM David Smiley
wrote:
> Much better Cassandra; thanks!
>
> BTW I notic
Much better Cassandra; thanks!
BTW I noticed some small differences in field order on the create screen
between Lucene and Solr. Solr now has the Environment field at the very
bottom whereas Lucene has "Lucene Fields" and "Labels" below it. Doesn't
matter I guess.
On Tue, Jun 12, 2018 at 10:29
OK, this is done.
I was rather aggressive about removing fields for the SOLR project that I
know we don't use, but much less so for the LUCENE project. I did ensure
that the Environment field is after Description in both projects.
I used a mix of looking up the field description in JIRA, querying
Sure, David, I'll do it this morning.
When I looked at the fields list for the form in JIRA, there are over 100
fields set up to display on that form - there's some other bit of arcane
JIRA configuration that defines the fields available for the project - but
I'll remove all but the ones I know we
Cassandra, can you please try editing the JIRA config to re-order
Environment below Description? I suppose Atlassian chose the current order
because it matches the order it's seen when viewing the issue, which makes
sense but I don't mind sacrificing that -- whatever it takes to diminish
Environme
+1 to try to fix the form ourselves, thanks Cassandra. I think putting
Description above Environment will do the trick. (I just created an issue and
put the description in the environment field…)
--
Steve
www.lucidworks.com
> On Jun 8, 2018, at 8:44 AM, Cassandra Targett wrote:
>
> I've bee
On 6/8/2018 6:24 AM, David Smiley wrote:
> Many of us have accidentally added a long-form description of our JIRA
> issues into the Environment field of JIRA instead of the Description.
> I think we can agree this is pretty annoying. It seems to have been
> happening more lately with a change to
I've been debating saying something about this too - I think it happened
when INFRA added some text to direct users to use the mailing list or IRC
if they really have a support question instead of a bug (INFRA-16507).
The most basic solution is a simple re-ordering of the form, which in JIRA
is re
+1 David
Just moving it below the description would also help, or making the input text
box for environment much smaller or something.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 8. jun. 2018 kl. 14:24 skrev David Smiley :
>
> Many of us have accidentally added
On my screen at least I can't see the description field without scrolling
down. I have no idea what can and can't be done with JIRA but anything that
makes it visible again without scrolling has my +1.
Le ven. 8 juin 2018 à 14:24, David Smiley a
écrit :
> Many of us have accidentally added a lon
Many of us have accidentally added a long-form description of our JIRA
issues into the Environment field of JIRA instead of the Description. I
think we can agree this is pretty annoying. It seems to have been
happening more lately with a change to JIRA that for whatever reason has
made it more vi
12 matches
Mail list logo