Comments
-
Not directly. Jira is not written in Python, so you would need to build a Python engine into an App you can install in Jira to enable something that could start rearranging and adding to the UI.
-
I am sorry, but I do not understand the question. Yes, I see you use some custom fields for classes of service (a lot of us do, custom fields are intended to hold data like that). I am not sure what that has to do with "Kanban features". I do not understand what you expect from "classes of service (risk profile)". You say…
-
If you're on Cloud, that only has one version - "cloud". Atlassian upgrade all the Cloud services regularly and frequently, so you're "always on the latest version". I can't suggest much, I don't know what your requirements are.
-
Please, don't try reading the Jira database, it's not built for any form of reporting, and you will be writing really ugly, complex SQL. If you insist though, start with fieldconfiguration, but that's only going to tell you part of the story.
-
What do you mean by "customise" and how do you want to use python to do it?
-
Yes, that's what a post-function will do, run during a transition. You did not tell us when you wanted this field update to happen, so we couldn't tell you a lot more. However you want to do it, the code in the post-function is a good starting point.
-
I would check if there are directory-related errors in the logs, it may be that Confluence does not think the right people are in the right groups.
-
Look at the issue. There is a tools option on it, with things like delete, move, clone, etc. One option will be "convert to issue". This is not a move in the usual sense Jira means it, it is a conversion.
-
You do understand that this is a very bad thing to do to your people, and whomever is asking you to do this is wrong?
-
It should be a simple "get custom field value for X from issue Y", and then "expose it on to issue Z", which are things people do with Scriptrunner all the time. https://library.adaptavist.com/entity/copy-field-value-from-linked-issue is probably a good starting point, although we don't know if a scripted field might be…
-
I can't speak for the exam as I've not sat it myself, but I do have one piece of advice - even experienced admins and power users should check the exam guides and docs for the lists of things you will be tested on. The questions are divided into a series of subject areas (for example, email, macros, permissions) and you…
-
I'm afraid the only way (without unsupportable hacking) to get the default workflow back to using "open" is to rename the "spec open" status back to "open". This will affect all the workflows using that status. If any workflow needs a "spec open" status, you should add a new status for it and modify the workflow to use it.…
-
Jira is complex software, doing a lot of work for people who need all sorts of different things. This does make the administration and configuration complex, and hard work for admins. A good admin has traits and habits including, but not limited to: * Listening to the people using their Jira * Making it as easy as possible…
-
Frustratingly, you can do context by issue type, OR by project, but not both on the same field. So if you have two sets of values for a custom field and want to do it by issue type, it's global, for every use of that field in every project.
-
The changes you are asking for here are mostly changes to the underlying code in Jira. If you are on Cloud, you have no access to that, so you can't change it. If you have Server, then you do have access to make code change, but it's not recommended as your changes will be unsupported (if there's a problem and you ask for…
-
Start with a look at https://marketplace.atlassian.com/search?hosting=cloud
-
This project is set up as a "Software Project" (just under the title of the project). You need to change it to a "Service Desk Project" - try the arrow to the right.
-
Correct, there is a limit of 1000 active issues in total, on the board.
-
Jira Service Desk "Requests" sit in front of Jira project, in the "portal" configuration. See https://confluence.atlassian.com/servicedeskserver/setting-up-request-types-939926357.html to get started.
-
No problem, that means it's a Core business board. Issues in the "done" column of these boards will vanish after 14 days of inactivity - so if they're not edited or commented on etc. There is a button to show/hide issues that have dropped off at the bottom of the column, but these boards are limited to 1,000 issues, so…
-
What type of board is your "project board"? If you go to "configure board", it should tell you
-
Ok, that's not quite what I expected. Could you re-configure the gadget so it does list all the resolved issues and give us all the numbers? Although I have just had a thought - is it exactly 1,000 issues in done? If so, then you may have run into one of the limits, in that boards don't perform when you've too many issues…
-
The files that make up your Lucene index on the Confluence server have been locked out against writing and Confluence is unable to make the changes it needs to make. There are a number of things that might do this, but the most likely thing is you've run out of disk space. You'll need to log into the Confluence server and…
-
Jira is an issue tracker, so it "has form fields that a user can fill out" - that's what "create issue" does! And you can export the issues to CSV with all the entered fields. I would use the tools you already have! Set up a Jira project to capture feedback, add the fields you want to it, and if you want to be a bit more…
-
To add to that, I know of places that have moved to DC when they're headed over 6,000 users and some places using a single node (i.e. "Server") with 50,000 users. As Dave says, it absolutely depends on your specific needs, and number of users is only one factor to consider!
-
You could try some javascript to inject a display of the numbers, but remember that they will not be of a lot of use - the numbers will not go on to the issues (because they don't make sense on them)
-
Ok, then it sounds like it is something in the space permissions. Are they definitely named in there? Also, do you have more than one user directory?
-
You'll need to explain what MAX.gov is and what you mean by "label tag ICON" - could you give us a screenshot?
-
You need to use "convert to issue" on the tools menu in the issue view, it's not really a "move"
-
Ok, filters find issues, they don't say anything about what is in the issues (there's a small exception in that you can store a sort order with them, but that's all they might say about what they find) We need to come back to what reports you are looking at, as it's those which are choosing what to pull from the issues to…