You can't. Because you don't always know what the project is, and even if you did, the user might change it, and that would mean adding/removing the fields dynamically.
In short, it's a monumental pain to try to do this dynamically, and there's little value in doing it.
8000 is still several thousand too many to be useful. To see what fields are used in a project, you will have to read through the screen schemes, field configuration and field contexts for each field to work out which ones are valid. Seriously, I think you've got a broken approach to your requirements here. Could you explain what you're trying to do that means you'd end up with 8,000 fields?
Sharepoint into JIRA? That does not make a lot of sense. Jira is an issue tracker, Sharepoint is where documents go to die. They're for very different things. I'd suggest revising your data requirements (if not the software choice) - what are these 8,000 fields actually for? Screen schemes, context and field configurations work together to present the user with fields set up in the way they need them. See https://confluence.atlassian.com/jira/configuring-fields-and-screens-187859099.html for a starter (the diagram is quite handy)
I've worked with Confluences a couple of hundred times that size. But you need to think about what you're doing. Confluence can handle documents as attachments, but it is NOT a management system for them. If you want to store static document *objects*, use a document management system. If you want to store documents as living pages, then Confluence is an excellent choice.
No, that's the point. An attachment in both JIRA and Confluence simply sits on the issue or page you put it on. No trees or folders, minimal metadata, basic searches. They are not about document object management, one is for issue tracking and processes, the other for writing things (including documents) as *live* pages. The last time I was lumbered with Sharepoint, we converted it properly - wrote a script to import all the required word documents as Confluence pages. Once they became live pages, the users actually started to use them.
Hello Grzegorz, If I could suggest one other thing (otherwise you will exhaust @Nic Brough [Adaptavist] completely) please have a look at a very good course in JIRA administration by Lynda.com here: http://www.lynda.com/JIRA-tutorials/Installing-Administering-Atlassian-JIRA/191943-2.html Only $25 and you will save yourself a lot of self-discovery and ploughing through the Atlassian documentation.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Community! me again 🙂 If you’re a marketing team using Confluence, we want to hear your story! How did you start using Confluence? What are your use cases? What have been some of the benefits?...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs