Comments
-
Put something on the issue that indicates it is for one of the 2nd line teams, and then define queues for each team. The teams can change the indicator if they need to swap it to a different team.
-
This is an error from the operating system being passed up to the server. The server has tried to write data to /home/atlassian/data/confluence. The operating system has not let it. This could be a range of errors but the most common ones are: * changed permissions blocking file write * running out of disk space * running…
-
You need the field on the edit screen to be able to set it. Your REST command has sent it, but the field is not there to edit.
-
JSD does not really expect "team" changes, it works more from "queues". People are expected to look at queues to help them choose what issue/request to pick up next. Mostly queues will be defined by urgency (next most likely to breach SLA), but there's nothing to stop you using a team indicator as well as SLAs (or even…
-
It depends on what you mean by "service desk user". That's an unclear term when talking about JSD. There are three types of user that matter as "service desk users": * Service Desk Agent: Can edit the issue priority in the issue screen by clicking Edit or on the field * Jira User: Can see the issue, but only comment *…
-
"it's not letting me" does not tell us what is wrong. Can you not type in one or both boxes? Add is non-responsive or goes grey? Clicking it gives you an error? What is the error?
-
As an admin, you can subscribe groups to it, and remove those subscriptions, but if people have personal subscriptions to it, thre's not a lot you can do. Ask them to visit and delete for themselves.
-
I think that's an ideal case for using a Jira app - it's close to the developers, everyone using one tool in one place, but you don't need your own servers and systems as your needs are not intricate and bogged down in business "needs" and legacy requirements. Qmetry is a good candidate for you.
-
Jira's only built-in option is a "subscription" which should list up to 50 issues and a link to the filter that it is being run on. You should be able to go to that filter to confirm what it is. Then as an admin, you should be able to use "manage filters" to remove subscriptions (or brute force and just delete the filter…
-
It doesn't have to be Confluence, it's not the only thing that runs on 8090 by default (and the list grows massively when you remember almost anything can be relocated on another port) Run a command line as the administrator, and then run netstat -ab From memory, that will list the open ports and processes. Try the switch…
-
You should look at both options really. Some people build tests into their Jira and don't use anything. Some people integrate complex test utility suites in with Jira because that works best for them. Most people would benefit from testing done in the same system as the development tracking though, so I would lean towards…
-
Did you give it a DC licence? (It'll work with a Server licence, but won't enable the DC functions. Evaluation is fine)
-
Approvals are a function of Service Desk, not Core. So no, you can't do it on Core. The closest you can get is to build your approvals as explicit workflow steps - have "waiting to approve" and "ready for development" joined with an "approve" transition that has a "condition" of "only people in the approval role/group" on…
-
Yes, you can get 25 and 10 for a total of 35. The people given the 10 Software licences will be able to use boards, the 25 Core/Business users will not. App tiers are by the largest application set you have, not the total, so yes, you will need to licence them all at 25 (even if the app is purely for software, you still…
-
Again, without a backup of the pre-upgrade database, there's no way back. Not without potentially months or years of work to downgrade the data, or just starting with an empty 6.4.5.
-
Ah. Ok. You only have one realistic option now - roll-forwards. Install an empty Jira 7.9.2 with a separate database, get the basics working, then stop it, repoint it at the 7.9.2 database you have with data in it, restart it and re-index it all. Without a backup of the pre-upgrade database, there's no way back (without…
-
Sounds like you "downgraded" the application but did not restore the pre-upgrade database before you started it. Stop Jira 6.4, reload the pre-upgrade database and then restart it, you should find it woks fine.
-
You're close, but not quite looking in the right place. You've looked at the workflow Step (has a 1:1 relationship with Status), but you really want to be looking at the workflow Transition between status. Post functions run on transitions.
-
All "scrum" projects are "Agile".
-
Please read the answers/comments added today.
-
It's the same answer - projects are not "scrum" or "kanban", those words are just to select a board type to create alongside a Software project. It's not stored, so there can't be a REST API for it.
-
That sounds like your board filter excludes done, or it is not mapped into a board column.
-
It's still a global setting
-
No it is not. I never suggested anything of the sort, so I don't know why you're asking for confirmation. As I already said, it's a global setting.
-
It will only look at the last column, I'd guess that you should probably have that in the last column as well. Assuming you want it to burn-down there.
-
You'll need to do this with groups, roles and permissions (I'd recommend using roles as much as possible). You need to remove whatever is granting this user access to the projects they should not have access to, and only grant them the single project.
-
Ok, so the last paragraph applies, you need to treat it as a list.
-
Is the field a multi-user picker? The name suggests it might be?
-
There's an example of setting lots of different field types over at https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/postfunctions/set-issue-attributes.html On the section that sets the custom user-picker field, replace the "get user by name" function with a simple issue.getAssignee() Although, I guess the…
-
Check the "where's my field" and "available fields" that should be under a button towards the top right of the screen.