Comments
-
Ok, so when you use this transition, can you compare the behaviour of an old and a new issues? Specifically, does the resolution appear on screen during the transition, and what value is in it by default?
-
Ok, what SQL driver are you using? Should be able to see it in the system information page.
-
So you are saying they are going through the same transition?
-
You have to remove the field from the edit screens, then amend the workflow, giving it transitions that allow editing of the issue, with conditions that prevent the "wrong" people being able to get into them and validating that only the right settings are set by the right people. This is hideously clunky, and it sounds…
-
It is a bit more complex. Off the shelf, there's a 1,000 limit, but you can override it with a parameter in the url. As lots of people then break things by using that parameter, there's a setting admins can set that locks it down, banning the parameter as well (or rather, restricting it to certain accounts). It's likely…
-
>Security Level appears on my issues configure screen, It needs to be on the Create and Edit screens, not just the "issues configures" screen. That's where the "where's my field" will take you.
-
No, JSU and JMWE do different things, albeit with some overlap. One is not a direct replacement for the other, unless your usage is limited to the places they overlap. Even if you are using related functions, the names in the config are totally different. Imagine a really simple case where you have a "post-function that…
-
Have a look at the workflow for the old and new bugs - what transitions are in use for the "resolve" transition, what are the differences between them? Look specifically for the post-functions and screens in use on the two flows.
-
There's no "custom field permissions" for any Jira system, without using apps that add the functions. You've found docs for a (Server only, I think) App that does it.
-
Do not do that. Assigning a generic user will mean you don't know who is the actual assignees, and I can guarantee you that will hurt you in the log run. It breaks your audit system and (technically, although generally ignored) breaches your licence.
-
Solution for what? The system is handling security levels correctly.
-
You do not get access to the logs in Cloud. You'll need to diagnose the 503 on the application you are trying to connect to the Cloud system. The 503 means it cannot reach the Cloud service, which either means it's offline, or your network is stopping it getting there.
-
It's not so easy for workflows, as they're indirect, but for the workflow schemes, just go to the list of schemes under Admin -> Issues -> Workflow schemes, and you'll see each scheme is listed with the list of projects that use it. That makes it easy to id the ones you can rename to indicate fully inactive. Once you've…
-
I think you have misunderstood my answer. There are no "options for inherit", it is done automatically.
-
As an admin, go to Admin -> Issues -> Custom fields. That's a list of all the custom fields.
-
You could use ScriptRunner to duplicate the field, but that's annoying for admins who are often engaged in a running battle with fielditis, and confusing for users who would not expect a field in one tab to update another one.
-
On Cloud they probably are part of the project, they only need read-access, which is the default. There's no point mentioning people who don't have any access to something - they won't get told they have been named, and it doesn't give any other functions.
-
A component is a sub-division of a project. They are there to help you categorise parts of that project. It's common do do things like User-design, web front end, database, process code etc for software, but you would equally define steering, doors, engine, seating, brakes etc it the project was a car. Components are…
-
You are probably being limited by the same as above - the missing people are not in groups that allow access to the issues.
-
There is a lot to be said for Atlassian's control of their platform. There are some absolutely appalling bad answers on Stack Overflow. As a "normal" user of Stack Overflow, I might be able to say that, but it's often one voted down by people who don't like being told they are wrong. As an Atlassian, they can't go on there…
-
Sorry for the delay on this, it dropped out of my list. Yes, this helps explain what you're looking at. Next-gen projects are a totally new way to set up projects, and have been designed without re-using the ideas from "classic" projects much. It is, allegedly, what most people want according to Atlassian's UI and persona…
-
What do you mean by "Jira pie chart"? (Obviously, I know what a chart is, but I mean what are you trying to create and where? Jira dashboard gadget? Jira report? External report?)
-
Cloud Core/Business boards, and Next-gen boards do not have settings, so I suspect you're using one of those types.
-
What is your connection string in the dbconfig.xml file?
-
The "can't create thread" is almost certainly down to "can't get a good connection to the database". Have you checked the error message given in your first line?
-
Yes, correct.
-
You should use whatever tool that created the .bak file to create a new copy of the database, then hook up another Jira to it. I'm afraid "could not start Jira again" does not explain what the problems are. What does the log file say the failure is?
-
Create a new field of the right type (single select), and then remove the old field.
-
Not in Cloud. On server, if you're careful, you can convert single-select to multi-select with an SQL update and a re-index, but you have no access to the database on Cloud. Your only option is to make a new field, then use bulk-edit to copy the values from the old field into it.
-
Best you can do is create a url field and post the full urls into there. If you have an automation or scripting tool, you can go a step further and possibly auto-generate it from a user entering the plain number.