Comments
-
It's for sharing with people who have permission to see it.
-
Yes, you need to be a Jira admin to edit screens.
-
That suggests you are not an admin. As an admin, you need to get into the screen with that name to check that the due date is included there.
-
That's also good. Now click on any of the links to TT: Scrum Default Issue Screen
-
Could you explain what this has to do with Bitbucket?
-
I've seen this when: * the index has had a problem - try re-indexing the project * someone has messed with the Epic fields (by unlocking them and changing things) * someone had changed the field context for the Epic Name - go to admin -> custom fields and check that it applies globally, but only for the Epic issue type
-
No, that's fine. Descend into the one which matches the issue type for the issue you are trying to get the due date on to.
-
Please, don't touch the database, it can easily go horribly wrong. You would be better off either * Changing permission scheme A so that it does the same as B * Getting something like ScriptRunner so you can script a bulk permission scheme change (I'd do the first, it's the easiest option)
-
Sorry, I'm not sure what netto/brutto means in English, so I'm not sure what feature of the time log you are referring to.
-
Your other option is to remove the "do not edit" flag from the "Closed" status. Or, limit the permission to just administrators. Workflow properties on status are your friend for that.
-
Ah, given that you're now getting errors in system add-ons, I would say yes, you should go back to 6.4 and step through to 7.0
-
No, it's locked mostly to prevent people adding it to the wrong thing. It would not appear here even if you unlocked it though. Jira hides fields that are empty on the issue view, barring some special ones, and the Epic fields are not on that exemption list.
-
It's possible that the lack of upgrade via version 7 has broken something, but I can't imagine what it would do to that particular add-on's data, so I think you might be alright there. Yes, I would move the kintosoft_subversion_h2 directory somewhere else and retry.
-
Jira Core only has simple "business boards". These are Kanban-like and do your create/move/complete, but have no configuration settings. Things drop off them after they've been done for a fortnight, columns are 1:1 with status, and they don't have resource tracking functions. Plus, these boards do not exist on Server, only…
-
Yes, the risk with the html macro is wider - anyone with "edit" could inject malicious code, not just your admins.
-
Have you tried google spreadsheets? If subtasks are not working for you and you need a spreadsheet, then I'd use spreadsheet software. There is a table grid editor add-on for Jira which embeds tables, but it's not a spreadsheet.
-
I'm afraid not. Filters are simple flat saved blocks of JQL. Some reports, functions and gadgets will take filters and allow some drill downs, but it depends very much on the report.
-
Yeah, I find it confusing and slow as well. It should be a single download page of all versions ever, although I'd grid it up for Jira 7 and probably do expansion areas. i.e. First open page: > 7 Expand for a grid with Core, Software and Service Desk (which would give you a compatibility matrix for the apps too, another…
-
Bother, I think that may have arrived in 7.3. However, your description sounds like you should check the screens in use. If you can see the field on view, but not edit it (and you have schedule and edit permissions), then it's not on your "edit" screen for this project and issue type. Have a look at the project's "issue…
-
They've annoyingly buried it several layers deep. Go to the main current download page, and look for older versions on the left. It pops up a display of "7.7" again, which it's not clear that if you click on, is actually a drop-down with 7.6, 7.5 ... 7.0.
-
The doc has a section "Editing a sub-task issue type", but you've already found what it says. If it's not available on a sub-task, then there's a permission in the way, probably that you are not allowed to edit it. Admin permissions have nothing to do with issue permissions. I think you've already got "bulk edit", but I…
-
Correct. Where the option is missing, you are not allowed to change it. You should find that on mostly locked and system fields. They're like that for good reasons.
-
What version of Jira are you on? You are on the full edit screen, not one of the board ones? As below (far right)
-
Two things 1. When you upgraded, did you go from 6.4 to 7.0 before going to 7.7? There is upgrade code in there you need to run for quite a lot of add-ons. 2. If you did take that route, then yes, the problem is definitely that add-on. Try removing it. Go into the home directory for Jira and find the "plugins" folder.…
-
Ah, no, that's not been done. I'm not sure they will either - board loads are very intensive, and if you've got a lot of updates, you could effectively lose your board for several minutes with repeated refreshes.
-
They all do the same thing, it's just useful for humans to be able to use different labels when linking issues. There's no way to stop them choosing any of them when they link.
-
It sounds like you've checked most places, but missed something. Could you go to "edit" again (full edit, not in-line) and look to the top right for "configure fields". In that drop-down, there should be a "where's my field" option. Ask it about "due date", it should tell you why you can't edit it.
-
The hierarchy in Jira is Category -> Project -> Issue -> Sub-task. Software and Portfolio can add higher levels over projects (Epics from Software, Themes and Initiatives in Portfolio). There is also the Structure add-on if you want to build something that looks like more levels, but I urge caution - it tends to mean…
-
Not natively, but you could easily do it with a different approach. If you edit the workflow, and go to a status, you can enter "properties". One of these is something like jira.permission.work . If you add that to a status and set it false, then a user can't log work when the issue is in that status. So they'll be forced…
-
It is in a stable format. For a given version. The format of json responses rarely changes. Most releases of Jira leave it untouched, although they do add functions and data. Jira 7 went through some major refactoring and one part of it was changes to the REST API. You should find that the json format will not change until…