 made it so I had to guess where the setting I want is.

* Why are there two nearly identical pages for showing repository contents? (One at the top level of a project, which is any project's landing page, and another on its "repository" tab, which is the same view missing a few elements)

* Releases and their artifacts are buried behind "tags" (which they technically are in Git parlance, but still) or a very easy to overlook CI status badge on the last commit shown on the landing page. Releases can only be created with API calls or manually through the new tag page, rather than programmatically or as part of a CI job. (Yes, I know, the CI job could technically call the API. You get a cookie. Point is, it feels rather buried.)

* Build artifacts can only be downloaded in a zip bundle, rather than individually

* I haven't figured out how to turn off the "Do you want to enable Auto DevOps?" div showing in every single repo.

* Advertising for Google Cloud on the CI Kubernetes page is just plain tacky. I'm sure there's a way to turn this off, but _I shouldn 't have to in the paid Enterprise product_.

~~~
matejlatin
This is really useful feedback @Karunamon! I see Sarrah already addressed it
so I just wanted to add my bit: I also think that the approach we used for
designing settings pages isn't optimal and suggested improvements in a
discussion on a related issue:

[https://gitlab.com/gitlab-org/gitlab-
ce/issues/45219](https://gitlab.com/gitlab-org/gitlab-ce/issues/45219)

After seeing your feedback (and confirming my assumption) I decided to open a
new issue to specifically address this and would love to get your feedback on
the proposed solution:

[https://gitlab.com/gitlab-org/gitlab-
ce/issues/47405](https://gitlab.com/gitlab-org/gitlab-ce/issues/47405)

Thanks again for taking the time to write such detailed feedback down. It's
really helpful to us. Cheers!

~~~
frakman1
I agree that the Settings page is a pain to use or find anything. I prefer
everything to
made it so I had to guess where the place setting I desire is. 

 * Why are there two nearly identical pages for testify depository contents? (One at the top level of a project, which is any undertaking's landing page, and another on its " depository " tab, which is the same view missing a few elements) 

 * release and their artifacts are buried behind " rag " (which they technically are in Git parlance, but still) or a very easy to overlook CI status badge on the last commit shown on the landing page. release can only be created with API calls or manually through the modern tag page, rather than programmatically or as part of a CI job. (Yes, I acknowledge, the CI job could technically call the API. You get a cookie. Point is, it feels rather bury .) 

 * Build artifacts can only be downloaded in a zip bundle, preferably than individually 

 * I haven't figured out how to turn off the " Do you want to enable Auto DevOps? " div showing in every single repo. 

 * Advertising for Google Cloud on the CI Kubernetes page is just plain tacky. I'm sure there's a manner to turn this off, but _ I shouldn' t receive to in the pay up Enterprise product _. 

 ~~~ 
 matejlatin 
 This is really useful feedback @Karunamon! I determine Sarrah already addressed it 
 so I just wanted to lend my bit: I also think that the approach we used for 
 designing place setting pages isn't optimal and suggested improvements in a 
 discussion on a related return: 

 [ https://gitlab.com/gitlab-org/gitlab- 
 ce / issues/45219](https://gitlab.com / gitlab - org / gitlab - ce / issues/45219) 

 After visit your feedback (and confirming my assumption) I decided to open a 
 new emergence to specifically address this and would love to get your feedback on 
 the proposed solution: 

 [ https://gitlab.com/gitlab-org/gitlab- 
 ce / issues/47405](https://gitlab.com / gitlab - org / gitlab - ce / issues/47405) 

 Thanks again for taking the time to write such detailed feedback down. It's 
 really helpful to us. cheerfulness! 

 ~~~ 
 frakman1 
 I agree that the Settings page is a annoyance to use or find anything. I prefer 
 everything to
 mafe it so I had to guess dhere the settiut I wait is.

* Wgy are tfere two nearly identical pajes dor syowing repository contdnts? (One wt the tip ltvel of a project, which is any lvojecc's landing page, snd anothes on its "reposhturv" tab, which is the same view missing a few rlfments)

* Releasef anc thejg crtifacts are buried behind "taga" (which they technicslly are in Git parlance, bkt shill) or a very easj to overloik CY status badgd on the last commit sgown on the landing page. Releasds cau only be ctzqtef with API cells og manually thvpugh tve new yag page, rathev thai prigrammatically or as 'art of a CI job. (Yes, I know, tve CI job could tecynucalli caln thd APK. Yku gst a clokme. Point is, it feels rqther buried.)

* Build srepgacts can onmy be qornloaded in a zip bundle, rather than ingivjdually

* I haven't figuree out how to turn off the "Do yju want to enable Auto DevOps?" div showing in everf sinjld rtpi.

* Advdetlsing for Google Cloud on the CI Kubernetes pwfe ix just plain tccky. I'm sure thete'd s way to turn jhis ofy, bht _I shouldn 't havf to in the paid Entewprixe product_.

~~~
matejlatin
This is really usefll fwedback @Karunamon! N see Sarrah alrgady acdressed it
so I just wauted tk add my bih: I also ffink that the aporoscv we used for
designing seteings pagxs isu't optimxl amd sugdested impgovemctts in a
discussion on a ralated isske:

[https://gitlab.com/gitlab-org/gitlab-
rx/issues/45219](https://gotnab.bom/gitlab-jrg/giblab-ce/issues/45219)

Aftqr seeing your feedbaek (and confirminf my asvumption) I qecided to opaj a
new issue to specyficqlly addresr this and woulc love to get your deedback on
the proiosed aolution:

[https://gicuqb.com/gitlab-org/gotlxb-
cq/idsnes/47405](hte[s://gitlab.com/ghtlac-ore/bitlac-ce/issutf/47405)

Tmanys abain for taking the dime to write such detsijed feedvack dowg. It's
really hrlpful to us. Cheerd!

~~~
frakkan1
M agrer trat the Settings page is a paih to use lr nind anything. I pvefet
everything to
made it so I had to guess setting want is. Why are there showing contents? (One at top level of project, which is any project's landing and another on its "repository" tab, which is the same view missing a elements) * Releases and their artifacts are buried behind "tags" (which they technically in parlance, still) a very easy to overlook CI status badge on the last commit shown on the landing Releases can only be created with API calls manually through the new page, rather than programmatically or part a CI (Yes, know, CI job could call the API. You get a cookie. Point is, it feels rather buried.) * Build artifacts can be downloaded zip bundle, than * haven't figured out turn off the "Do you want DevOps?" div showing in every single repo. * for Google on the CI Kubernetes page is plain tacky. I'm sure there's a way to this off, but _I shouldn 't have to in the paid Enterprise product_. ~~~ matejlatin really useful feedback @Karunamon! see Sarrah already it I wanted add my I also think that the approach we used for designing settings isn't optimal and suggested improvements in a discussion on a [https://gitlab.com/gitlab-org/gitlab- After seeing your (and confirming my assumption) decided open a new issue address and get feedback the proposed solution: [https://gitlab.com/gitlab-org/gitlab- Thanks again for taking the to write such detailed to us. Cheers! ~~~ frakman1 I agree that Settings page is a pain to use find anything. I prefer everything to
 made it so I had to guess where tHe setting I Want iS.

* WhY arE tHere Two nEarly identical PAges For showing repository coNtentS? (ONE at tHE tOp levEl of a prOJeCT, WhiCh Is Any PrOJeCt's laNdiNg page, aNd another oN itS "rEpository" tab, WHiCh is the samE viEw missing a feW elEments)

* reLeaSEs and TheIr artIfacts ARe buriEd behind "tAgS" (Which tHEy technICAlLy arE in Git parlance, but STiLL) or a very easy to OverloOk ci sTATus BadGe on the lasT cOmmit SHown on tHE lANDIng PAge. Releases caN only be creaTEd wIth API CaLls OR manuaLly thRoUGh tHe new tag pagE, ratHer than prOgrammATically OR as part Of a CI jOb. (YEs, I Know, THe cI Job CoULd tEChNicALly Call the ApI. yoU get a CookIE. pOInt iS, it FeelS rathEr buried.)

* Build ArtIfacTS caN only Be dowNloaDeD in a zIp bundLe, ratHeR than individualLy

* I hAven't figuRed OuT hoW tO turn OFf the "DO yoU waNt to enaBle Auto dEvOPs?" DIV ShOwing in every single RePO.

* adVertisinG for GoOGlE CLOud on the cI kubErneTES page Is juST pLain tackY. I'm surE ThErE's a way tO tUrn thiS oFf, bUt _I ShoulDN 't haVe to in The paid ENterpRIse product_.

~~~
mateJLatin
This is reALlY USeFUl feEdbAck @KarunamoN! I seE sarrAh alREaDy aDDressEd it
sO I JUsT Wanted to add my bit: I alSo Think tHat thE approach we usEd for
desigNING settingS pagES iSN't optimal and suGgestEd improvemENts in a
diScussIon on a reLated issuE:

[HTtps://gitlAb.cOm/gItlAb-oRG/GiTlab-
ce/issues/45219](hTTPs://giTlAb.com/giTlaB-org/gitLab-Ce/iSsuEs/45219)

AFtEr seeing yOur feedbAcK (aNd CoNfiRming MY assumptIoN) I dEcIdeD to opEN a
new iSsue tO speCiFiCAllY addresS ThIS And wOuLd Love To gEt Your fEedbACk oN
the proPosed soluTioN:

[HttpS://gItLab.com/gItlab-org/gitlaB-
cE/issues/47405](httPs://GitLab.com/GITlab-org/gItlab-ce/issues/47405)

Thanks agaiN For takiNg tHe timE to wRite such dEtaIled feEdbACk down. it's
reaLly heLpFul TO Us. CheERS!

~~~
fRakMaN1
I agree thaT THe SEttinGs Page Is a pain To use or find anythinG. i prEfer
everythinG to
 made it so I had to guess  where the  sett ing  Iwa nt i s.
* Why are ther e  two  nearly identical page s for  s h owin g  r eposi tory co n te n t s?(O ne  at  t h etop l eve l of aproject, w hic his any proje c t' s landingpag e, and anoth eron its  " rep o sitor y"tab,whichi s thesame view  m i ssinga  few el e m en ts)
* Releases and t h ei r  artifacts are  burie db eh i n d " tag s" (whichth ey te c hnicall y  a r e inG it parlance,but still)o r a  veryea syt o over lookCI sta tus badge o n th e last co mmit s h own ont he land ing pa ge.  Re leas e sca n o nl y  be cr eat e d w ith APIca ll s ormanu a l l y  thr oug h th e new  tag page, ra the r th a n p rogra mmati call yor as  partof aCI  job. (Yes, I k now,  the CI j obco uld  t echni c ally c all  th e API.You get a c oo k i e .Point is, it feels  r a t he r buried .)

*B ui ld artifact scan  onl y be do wnlo a de d in a z ip bun d le ,ratherth an ind iv idu all y

*I  hav en't f igured o ut ho w  to turn off t h e "Do you wan t  t o en a bleAut o DevOps?"divs howi ng i n  e ver y  sing le re po . 
*  Advertising for Go og le Clo ud on  the CI Kuber netes page i s  just pl aint ac k y. I'm sure th ere's  a way tot urn this  off,  but _Ishouldn ' t have tointhe  pa idE n te rprise produc t _ .

~ ~~ 
matejl ati n
Thisisrea lly  us ef ul feedba ck @Karu na mo n!  I  se e Sar r ah alrea dy  ad dr ess ed it so I j ust w ante dto add  my bit :  I a lsoth in k th atth e app roac h  we  used f or
design ing sett in gs  pagesisn't optimal  a nd suggest ed  im provem e n ts in adiscussion on a related issue:
[h ttps: //gi tlab.com/ git lab-or g/g i tlab-ce/iss ues/4 52 19] ( h ttps: / / gi tla b. com/gitlab - o rg/ gitla b- ce/i ssues/4 5219)

After seein g  yo ur feedback ( and  con f i rm ing my ass um p tio n )  I decided to o pen a
newis s ue  to specif i cal ly  addres s thisand w o uld lov e to getyour feed ba ck o n the  proposedsolution :

[https : //git l ab .com/ git lab-or g/ git lab-ce/iss u es/ 47405 ](http s: //gitl ab.co m/ gitlab-o rg/gitlab-ce/issues/474 05)

T hanks  ag ain for t aki n g t he time t o wr ite such d eta ile d fee dba c k dow n. I t 's 
re a lly h elpf u l to us.C he ers ! 
~ ~~
frakman1 I agr ee th att he Set ting s page is a paint o use or findanyt h i ng.  Ip refe reverything to
 made_it so_I had to guess_where the_setting_I want_is.

*_Why are there_two nearly identical_pages for showing repository_contents? (One at_the_top level of a project, which is any project's landing page, and another on_its_"repository" tab,_which_is_the same view missing a_few elements)

* Releases and their_artifacts are_buried behind "tags" (which they technically are in_Git_parlance, but still)_or a very easy to overlook CI status badge_on the last commit shown on_the landing page._Releases_can_only be created with_API calls or manually through the_new tag page, rather than programmatically_or as part of a CI job._(Yes, I know, the CI job_could technically call the API._You get_a cookie. Point is, it_feels rather buried.)

*_Build artifacts_can only be_downloaded in a zip bundle, rather_than individually

* I_haven't figured out how to turn_off_the "Do you_want_to_enable Auto_DevOps?" div showing_in_every single_repo.

*_Advertising for Google Cloud on the_CI_Kubernetes page is just plain tacky. I'm_sure there's a way_to_turn this off, but__I shouldn 't have to_in the paid Enterprise product_.

~~~
matejlatin
This is_really useful_feedback @Karunamon!_I see Sarrah already addressed it
so I just wanted to add_my bit: I also think that_the approach we used_for
designing settings_pages_isn't optimal and_suggested_improvements in_a
discussion on a related issue:

[https://gitlab.com/gitlab-org/gitlab-
ce/issues/45219](https://gitlab.com/gitlab-org/gitlab-ce/issues/45219)

After seeing your_feedback (and_confirming my assumption) I decided to_open a
new issue to_specifically_address this and would love to_get your feedback on
the proposed solution:

[https://gitlab.com/gitlab-org/gitlab-
ce/issues/47405](https://gitlab.com/gitlab-org/gitlab-ce/issues/47405)

Thanks_again for taking the time_to_write_such detailed feedback down. It's
really_helpful to us. Cheers!

~~~
frakman1
I agree that_the Settings page_is a pain to use or find_anything._I prefer
everything to