Comments
-
Ok, so you need to write a large add-on. Start at https://developer.atlassian.com/server/framework/atlassian-sdk/create-a-helloworld-plugin-project/ But, please be aware that you still cannot do sub-tasks of sub-tasks. It doesn't matter how clever your code is, Jira simply doesn't support it in the core. You can botch…
-
Adding a field should not have that effect. It sounds like the permissions have been changed such that you no longer have access to the project.
-
I don't know what you mean by "service key expiration time"?
-
Use a multi-select list then, that restricts the options.
-
Your transistions have the wrong end-points. You'll need to edit the workflow and either rename the transitions or swap their ends over.
-
You have an add-on from https://marketplace.atlassian.com/vendors/1210728/brizoit which is breaking somewhere. Follow the links for support from that page.
-
Why would you want to do this? Jira already has a REST API that can create and edit issues, what is the reason for not using that?
-
The ability to delegate limited field changes is on the way, within 2-3 releases I suspect.
-
A board and sprint's definition of done is "in the far right hand column on the board". The status and category do not matter beyond the status being in that column. Make sure "closed in the workflow" and "deployed" are included in the last column.
-
I would rule out the migrate one-at-a-time approach - the process will involved repeated cycles of data hacking, cleaning and then importing. Doing the migration all in one step will be a lot faster and less work. Clean then migrate, vs migrate then clean, is a less easy choice. Part of me says clean first as that reduces…
-
Do you have a scripting add-on to do this with? You cannot create sub-tasks of sub-tasks.
-
Ah, you meant service desk, not core (I've amended your labels) The highlighting shows me where you're looking, but what does it look like without the highlight? And, do you really mean you are creating a new template, or just a new request?
-
Should be on the tools menu - the three ... to the top right. If you don't have create subtask in there, then the project does not have sub-tasks.
-
Ah, right, those are sub-tasks. It's easy to code a post-function to create them, and there are loads of add-ons in the marketplace that can do it as well. You don't need to touch the database, Jira does all that work for you.
-
You'll need to explain what a "request template" and "title" are, as Jira does not have those functions. If you mean Confluence, which does have templates and titles, then I'm a bit stuck on what you mean, because you need to click to edit the title, as you can't have a page without one.
-
If it is appearing for some people, but not this person, and the "configure fields" is not hiding it for them, then there is something wrong with their browser. Get them to try a different browser.
-
Look at the system information page, it lists the driver or at least the classes loaded (think it's listed the version of the active database driver since version 3)
-
You can't do this. Boards are a view of a set of issues, not containers for them. When you look at, or change issues on a board, you are affecting the issue directly, not the board. Boards order by rank. This is a field that exists on issues to enable Jira to put them in order. Because the rank is a function of the issues,…
-
Not natively. You could use behaviours in Script Runner to implement this for end users, but it would be quite complex. A better option is probably to use the multi-level cascading-select add-on, which is built for doing this. I don't know if the mlcs add-on supports non-admin maintenance though
-
That looks fine, they should be completely separated. You'll want to check the database logs as Guilherme mentioned.
-
Ok, so you can just use a text field with a little bit of code to populate it, or do you need something more complex?
-
It is odd. It's happened because of the way Jira evolved early on in its life, and it's something I would dearly love Atlassian to throw away. The field configuration says "field is mandatory", so you must enter it on the issue. The screen in this case is irrelevant to the logic of the field configuration, Jira just sees…
-
A step in Jira-speak refers to parts of the workflow (an issue goes through a workflow following a set of steps). You need to explain what a "list of step" is in world. What would a user see on the sub-task?
-
That is an add-on, not a built-in function. I don't know that add-on I'm afraid, so I can't help you
-
"Table already exists" suggests that you are pointing a new Jira install at a database that already has a Jira installation. Do not do that, it will not work. Install your Jira with an empty database. Or tell the installer to upgrade an existing Jira in there, not create a new one.
-
To add a column, click the "add column" button to the right. Columns are not added to a status. Columns are created and then status are put in them. If you want several columns to show your various in-progress status, you need to have those status in your workflow, and then map them into the columns.
-
<sigh> I really can't be bothered to respond to any of that. In your own words, you are wasting both my time and yours by ignoring what we're telling you. When you give us a list of errors and log entries, try acting on the responses instead of whinging. Yes, I talked in unix instead of windows when trying to help, but the…
-
I think you've found the right docs there, and they are right, but the cert you have for your LDAP server is wrong because it has been revoked by your network admins, or it has expired. Either way, you need to get a cert that works with your LDAP services. Talk to the admins of that service.
-
Ok, I missed the Windows install thing, for which I apologise. My only excuse is that you've posted vast amounts of stuff that I know isn't that important, and it's lead me to skim instead of read, and that was the wrong thing to do, and I should have read properly. To try to go over the problems when I red properly: Your…
-
You need to explain your random acronyms. I have no idea what Attention Deficit Syndrome or Alchol Dependency services have to do with the North British Railway, let alone Jira.