It really comes down to Atlassian's vision for the products, but this is just my understanding of it.
1.Why do i see custom fields from other projects when doing bulk changes on issues?
Bulk change is done from issue navigator - so as you can browse for any issues available to you, the bulk change must also accommodate for this, it's quite a generic page to begin with.
The other question is - what makes a field "associated" with issue. There are basically 2 components.
The first one is "human" way - is the field used in any of the screens for the issuetype in the project?
The second is the "technical" way (and of course the one Jira will use) - is the field "available" for the issuetype and this project?
And what makes it "available" depends on the field's context. What you're seeing in bulk change is all available fields - because it's simply that - they're available. Whether you are using them or not is not something Jira can really know, nor is it something it should try to know.
We might argue whether Jira possibly could learn to identify which fields you really want or not, but it will never cover each and every use case, because sometimes you want to do bulk changes on issues for fields which you are not - strictly speaking - "using", and there are use cases to using fields without having them on your screens - for instance some automations can use them "in the background".
2.Why creating issues form is showing me sprints and epics from other jira projects?
Collaboration, and that's what Jira's built around. You could for example have one project with just Epics, and then 20 projects per individual teams, so they need a way to link to the epics.
Same with sprints - multiple projects can work on the same sprint.
I believe that you are seeing them from other projects as there are lenient/public permissions on your instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.