Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! No, there's no way to do this. If you cannot identify someone, then you don't know that they should have any right to share your data.

Hi Fredrik No, you can not do this. If the macro is not coded as a distinct sub-module in an app, then you can not disable it alone.

As I said above.

Welcome to the Atlassian Community! You have two options. One would be to script something in Jira that can poke the information you want into your Django. The other is to do it the other way around - have Django ask Jira for the information over the Jira REST API. We can't give you much more than that - we don't know what…

If you can tell us what you were doing when the message occurred, then we might be able to tell you. For example, the error is one I associate with you making a REST call to create or edit an issue that has a create or edit screen that does not include the field. If it is that though, there is more error message that would…

That's not quite true. Basic Jira supports one child issue level. If you add Software, you get a third, and Advanced planning lets you add more (as do some apps)

Welcome to the Atlassian Community! Sub-tasks should not have sprint estimates on them, so Jira will not display it in the estimate column in the backlog. You could add it as a field in the backlog display if you need to see it, but I would not bother. If you have added story points to sub-tasks as the same field as the…

Welcome to the Atlassian Community! Simple answer is "no". Jira's issue keys are a simple <project key>-<sequence> In a lot of places Jira will display sub-tasks as part of their parent though, so at least you get to see "ABC-123 / ABC-234" where it matters.

Welcome to the Atlassian Community! That sounds like you've drifted into an unmitigated mess when you've got 13 fields to look at. You should really have at most three - the assignee, a team indicator, and a specific label. This lets you use simple filters, consistent ways of doing things, and has the flexibility to work…

I would very strongly recommend using an app. Synchronising two Jira systems is very complex, and trying to build something yourself is a massive undertaking. It's going to cost you a lot more to do that work than it is to licence an app to do it. I have done a simple version of a sync several times, always with…

Yes, those are the global fields I mentioned. They are not the TMP-local fields you have already got. You will need to move the data from the TMP-local fields into global ones.

No. As I said, the "active" display just tells you that you have one or more projects configured to use it. The tabs have nothing to do with it.

That is admin rights in a team-managed project. The stuff you are trying to change can only be modified by Jira administrators, and they mostly do not apply to team-managed projects.

Ok, on both a technical and procedural level, the field does not make a child reference. That is done with Sub-tasks, Issues, Epics, and any other issue levels you put in a hierarchy above Epic. This field is never going to act in the way a "parent" field will. But hey, if that's what they think they want to do, it's not…

No, you need to switch from using team-managed projects to company-managed projects. Jira Work Management project templates can mostly be of either type. Try creating a new "work management" project, and select "blank". Under the "name the project" and "type", there is a "show more" expandable area, which will let you…

Welcome to the Atlassian Community! You can not. Boards are supposed to represent a team's work, not an individual. The quick filters are all off by default because the board is assuming the visitor wants to see all the team's work, and then drill down with them after seeing the whole. What you could do is create a Kanban…

Hi Shivani, Admin rights are irrelevant here, they just give you the ability to administrate, not "can do everything". They wouldn't even help if you could do everything in this case. The problem looks like you have got a field that is set to be required, but not presented to the customer in the request page, so they…

It is the same answer as Jack gave you on https://community.atlassian.com/t5/Jira-Service-Management/Any-other-ways-for-viewing-Issues/qaq-p/2591867 Your first screenshot is of an old Jira Server view, one that Atlassian are moving away from, especially on Cloud, as you can see in your second screenshot. There is no way to…

To be clear, it is not "add the configuration", it is "change the schemes so that project A and B use the same schemes"

Welcome to the Atlassian Community! I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software. It is both - you should reuse where possible, but not be afraid to create new things if the project needs it. Company-managed projects…

Welcome to the Atlassian Community! The different ways that projects work reflects what they are for, and some of the features directly clash with each other, so you can't do both at once. That applies a lot more to team-managed projects than company-managed, you can pretty much change CMPs from one shape to another by…

That was one of the next couple of things I was going to mention if you could tell me that you had stopped using the database. Deleted and anonymised users will not give you useful information when you read the database instead of the UI.

Yes, very much so, if you get all the filters right. Filters, and so the boards and gadgets that use them are not containers for issues, they are views. Reconfiguring any of them is not going to touch your issue data, it will only change what they show you and how. Scrum and Kanban boards (from Jira Software) work off an…

Welcome to the Atlassian Community! The first thing to check is if the boards are Scrum boards. Only Scrum boards have sprints and burn (Kanban boards measure throughput rather than burn, and local team boards can be assumed look mostly Kanban too)

Welcome to the Atlassian Community! Jira does not have "sub projects", and I would recommend having another look at what sub-tasks are in Jira. I am not sure I have got the right description yet, as people seem to struggle a bit, but my current story is that they are a fragment of their parent issue, not really individual…

Ok, so the next question would be "what app are you using for this?" But your last line mostly makes it irrelevant. You say "I have created a view in the database". Do not do that. It is not going to do what you think it will. You need to swap to a gadget that uses the Jira API to read the data. (You have also invalidated…

Welcome to the Atlassian Community! Fields in TMPs are local to the project, they are not shared. Even if they have the same name and configuration, they are not the same field. The contents of components and versions are the same, for both CMP and TMP types! If you were to convert your custom fields to global custom…

OK, I'm not sure what you mean by "map the reporter field to export the data in gadget report". A dashboard contains a load of gadgets. Some of them can display fields like the reporter and assignee. There's no mapping or export in there. Could you explain a little further? Maybe a screenshot of a gadget doing this?…

No problem. You've already marked the answers right, which tells the Community "closed". We leave the questions in place in case someone else does a similar search, and it may be useful for them to see the answers that worked for you.

Welcome to the Atlassian Community! If they are showing the right name on view, then they are not wrong. Why are you looking at the database? It is the worst possible way to do any reporting on Atlassian systems, precisely because of this sort of thing.