Comments
-
That's not right, your 90 users will have access to the project screens, as you let them see the project. However, even if it were possible to hide them (it's not, without code, because it's useless to hide them), it's irrelevant. App licences must match the (highest) number of users you have for the applications you have.…
-
Go to the "create issue" process and look to the top right for "configure fields". In there, you should find a "where's my field" option, which will tell you why the field is not appearing. (Also, just check it's actually selected for display in there as well)
-
What part of bitbucket? PR? Commit? Browsing in a browser? Connecting with sourcetree or another client? Logging in? Everything? If it's everything, then look at the power of your computer. If it's stuff that requires exchanges of data between you and Bitbucket, then look at the network speed (are you near the servers, is…
-
Again, try labelText in the quick search. Or the CQL functions in the standard search
-
Have been for years (you've found a 5 year old thread). Although I'd totally agree with the "correct" answer, in that the UI for it is weak and the weighting algorithm awful Try labelText:chocolate in the search bar.
-
Indeed. Atlassian deliberately designed all styles of transitions to be immediately available to the users and a lot more simple to use than popping up boxes, which is extra clicks and makes the user think more, even though they've already decided what they're doing. On the view screens, transitions are a single labelled…
-
Those are errors that occur during the shutdown. You will need to look earlier up that file to see why it's not starting properly. Read atlassian-confluence.log and catalina.out for the times around starting it. One of those will tell you why it's not able to start.
-
>Our admins/devops dislike the product, our devs try their best to avoid using it, the analysts complain weekly about it, customer service use it long enough to copy paste to a second system. Our jira intern hates using it but loves that he has a job. That paragraph smacks of a Jira admin person or team that have not…
-
The list of possible assignees is determined only by the "can be assigned issues" permission in your project permissions. You can easily cut that from "all users" to "only people in a certain role in the project" (or other similar rules), but it's not done by request or issue type, it's all about the user's roles.
-
I answered that a couple of weeks back, over at https://community.atlassian.com/t5/Jira-questions/take-jira-new-update-s-to-bugzilla/qaq-p/785471
-
I don't know of any myself, that's why I left it as "you will need to find..."
-
That's a very generic error which could mean a lot of things. It usually means the licence key is simply broken (if it were an invalid version, SEN, for the wrong application, or in a recognised format that's incompatible, such as Jira v3 licence keys, it would tell you that) Is it a flat copy and paste of the whole key in…
-
Move can't restrict the landing point, no.
-
You will need to find or write an add-on that can do that.
-
An issue can only have one status, that's the point of a workflow. The usual way to do what you need is to take a different view. Create a board for each team. For the Front End team, have "ready for test" as the far-right "done" column, and for the BE team, it's the far-left "to do" column
-
You need to open the port in the firewall, so the application can use it. You can turn Synchrony off and revert to non-collaborative editing (Admin -> Collaborative editing -> off) if you don't want to open the port.
-
The licence belongs to an Atlassian account (uniquely identified by email address), but that does not matter to the system being licenced. I've used plenty of licences provided by other people on systems where they don't even have an account. What is the error message you get?
-
Correct, because you don't need one. Most people grasp that intuitively when introduced to Confluence. It's not a developer blaming the user, it's another user pointing out that you've misunderstood something.
-
Yes, after a bit of triage as Morgan mentions.
-
Change workflow settings? Could you explain what you've done in full to get this to the one case where there's a possibility it might be a safe thing to do? (And the fields?)
-
You have an add-on which is configured to block sub-task creation in certain states. It's giving you a validator on the "create issue" transition for the sub-tasks, if I have understood the description of the behaviour in your question correctly. You'll need to get your admins to reconfigure or remove it.
-
Every single one of the 600,000 issues you've mangled the data on. Your SQL ignores all the configuration checks and data consistency that is required. Where are the checks on field consistency? Workflow settings?
-
I don't think you've grasped what the software does. There is a hierarchy, which makes "folders" redundant (at best, a primitive way of thinking). Go to a page anywhere (let's call it page A), hit "create page", put something in it and save it as Page B. You now have page B in the hierarchy under Page A. You can move it…
-
Jira Service Desk layers portals, requests and SLAs over issues, projects, workflows and fields. Those things are only provided by Jira Core. In some ways, Atlassian encourage you to think of the Jira "family" as nine different applications (Cloud/Server/DC * Core/JSD/Software), but it's not quite right. Jira Core acts as…
-
NO NO NO. NEVER DO THIS.You will break your Jira if you do this (except in one very very specific case, which we would still very strongly recommend you never do as well).
-
Your form will need to have some code that can issue a REST call to your Jira system with a "create issue" command. See https://developer.atlassian.com/server/jira/platform/rest-apis/
-
Not natively, but Apps like Tempo Timesheets can do it.
-
Either check the transition screen has those two field, or stop trying to set them in the call to make the transition.
-
As an admin, edit the project and set the "type" to "Service Desk". That said, re-imagining the whole thing so your customers become SD customers instead of Jira users may not be as simple as "flip the type", and probably needs a bit more thought. Are you sure you want to demote the users to that level? Do you still need…
-
Oh, I am sorry. You said you had set this all up, so I assumed you were a Jira admin. To edit a workflow, there are a number of criteria you might match * A simplified workflow. Project admins can edit these via the boards, after a Jira admin has set the flag to allow it. They can add/remove columns and status via the…