Comments
-
Try installing the Jira toolkit, then adding a custom field of type "Participants" I already said you'll need to write functions to do exactly what you have described, the participants field will get you closest without having to write code.
-
<jira home>/logs/atlassian-jira.log should give you the full error
-
Could you please tell us which Atlassian product you are working with?
-
Most testers using Jira will reach for an add-on to help them. Jira is an issue tracker off-the-shelf, and does not directly support test plans. To give you a rough idea of why that matters, think of a "to do list". You have stuff that needs doing, so you write down each item, and then cross it off when you've done it.…
-
Because every Bugzilla that Mike and Scott ran into had a severity field that contained utter rubbish. They dumped the field because it was (and still is) usually useless. I still work with systems where it's built in, or been added, and that still stands. It's not that the idea of a severity is wrong, the problem is that…
-
We usually use the word "instance" to talk about a single Jira installation. Imagine I download Jira. I take the installation files and copy them to three computers and run them. At the end of the installation, I have three separate "instances" of Jira. Three separate urls that they run on and isolated data-sets. Now…
-
We cannot help you until we know how you want to represent your test cases in Jira.
-
The solution is to read the warnings the upgrade process gives you about the files it is going to replace and look at the differences between old and new. The installer cannot know what you might have done to the config files, so it has no choice but to replace them with ones that it knows work (as a new version could…
-
How are these "templates" being done? (Jira doesn't have issue templates natively)
-
Start at https://developer.atlassian.com/docs/ - I think you probably need the "Jira Software Server" one towards the bottom left (which in turn links to the Software REST and internal Java APIs), but there may be others you'll find useful.
-
I think we need to see a lot more of the log to diagnose this one. The application log will have what you've posted, but a lot longer, and I would like to see what it says from that point down to where it has moved on to lookingat something else.
-
I would stick with Jira, but make it a bit more robust. Have a specific issue type of "project request", so that you can customise it heavily: * Simplify fields down to "desired name" (mandatory, and even consider just using "summary" for it) and something to describe the initial permissions * Workflow is probably not a…
-
There's two steps: First, re-index (a background index will be fine, or even just project index if you are only working with one project), and have another look at the results. Second, you'll need to go into a proper debug routine. Issue statistic gadgets are very simple and reliable, and for a statistic like status,…
-
You have a custom field called "Beta QS" in your system. Your new project has a "field configuration scheme" that says this field is mandatory. You either need to change the scheme to make it optional, or place the field on the "create issue" screen.
-
How are you recording the "release version"?
-
Yes, you use the REST interfaces directly to connect them. Again, I can't tell you much more than that because "integrate" tells us nothing.
-
Licences have not added users since version 4. There's a single licence that says "you can have up to <tier> number of users. What you've done is replaced a 50 user licence with another 50 user licence. What you needed to do was upgrade your existing 50 user licence to a 100 user licence. If you get in touch with Atlassian…
-
I'd strongly recommend 5.2 -> 6.4 -> 7.0 -> 7.8or9
-
Pages that don't have content other than macros that pull in data from other pages.
-
Ah, ok, but it's the same answer. Your validation is checking for the resolution field, but your user has not entered it.
-
You'll need some code to do this, one of the scripting add-ons would probably be easiest as they would let you write whatever logic you want. A word of caution though - you'll still need to ask people to enter the summary on issue creation, despite the fact your listener/post-function code will scrub what they enter. You…
-
Yes, I completely understand what is happening. People are estimating time on subtasks. Scrum in Jira Software does not support that, it ignores the estimates on subtasks because you are committing to stories, not parts of stories.
-
See the answer from Ricardo four years ago.
-
You will need to increase your current plan, there is no "separate account" (unless you mean a completely separate Jira with different data and just that one new user)
-
The closest you can get without code is the issue navigator.
-
They don't any more, they get your tech contact to delete.
-
It's not a move, it's "add the users to the new group, then delete them from the old one"
-
There's no way to do this. Each of your logins is a separate "Atlassian account", and hence are different users in the systems.
-
Including columns needs add-ons, as the excerpt only works on blocks of content (i.e. the whole table!). For future pages, I'd build a page template that has the excerpt setup you need and some instructional text for the users using it.
-
Hmm, sounds like an indexing problem. It should appear immediately.