Comments
-
You'd need to ask an Atlassian developer with knowledge of the back-end. I do some dev work in plugins, but I never go to the database, I use the API (if you think you need to read a Jira database in your code, you're probably doing something wrong. And you never write)
-
The closest you'll get is https://developer.atlassian.com/display/JIRADEV/Database+Schema
-
The property "do not edit issue in this step" is totally independent of the transitions. Think of them separately. The property JUST stops people using the EDIT function. Transitions have nothing to do with it.
-
Let's say you've added user-picker fields called "Dev resource 1" and "Dev resource 2". All you should really need is a filter for "dev resource 1 = user A or dev resource 2 = user A". Reporting is a different matter though, my instinct is that you're not really having a problem finding the issues, more getting information…
-
You don't need to do anything. The licence format changed between 3 and 4. Any licence provided after version 4.0 is valid through to the current version.
-
If the visible ones are not sequential, then that supports it creating ones you can't see for some reason. Could you have a look at the permission and security scheme for the project?
-
Ok, that implies you are somehow creating issues that are completely blocked from your sight. When you run that query, what issue numbers come out? Let's say you created them with summaries as you said, 1, 2, 3, 4, 5, 6, 7, 8. Are the issue keys TEST-1, TEST-2, <missing 3>, TEST-4? Or sequential?
-
Ok, great, that rules out some stuff. Next question is what is the definition of the "filter for test board"? Is it really simple, like "project = test"? Do you see all 8 issues if you go to menu -> issues -> search, click "advanced" and paste the query into the search defintion? And was the "create issue field" the one on…
-
You have a big pile of issues in JIRA. Your board is a view of the pile, and it says "only show issues that match these criteria (e.g. it's written on a green note)". There are some further "quick" filters that enable you to toggle more criteria (e.g. only show me notes written in block capitals) You are creating issues…
-
It means your board configuration is not including the issue for some reason. The board filter is often the culprit (e.g. the board says "all bugs and stories in project X" and you create a request-type in project X), but check also the columns (do you have the "new" or "open" status in a column?) and the quick filters in…
-
Yes, you can add an issue link.
-
I'm not sure I can. You need to look at your account or your system information page. I don't know what else I could tell you.
-
Look in your my.Atlassian account, or in the system information page in the application.
-
duplicate of https://answers.atlassian.com/questions/37008/propleme-whit-log
-
Status is an indicator of where an issue is in its lifecycle, it has nothing to do with the assignee. "Status = assigned" is the wrong approach here, just because you assign it or unassign it, doesn't mean the status should change. The assignee is who owns it at the moment, not where it is in the workflow. If you insist on…
-
Summary!
-
Yep. For each issue you want to look at the links for, use an issueLinkManager call to get the list of links and then check the issue at the end of each one in order to see if it's in the target project For example - links = issueLinkManager.getLinkCollection (issue, user, true) will return all the links on an issue, as…
-
That doesn't really make a lot of sense. Links are between issues. I suspect a better way to put it might be "when looking at an issue, I want to get the links (or issues?) to issues within a specific target project". e.g. ABC-123 is linked to ABC-456, DEF-234, GHI-567 and DEF-345, so you want to get DEF-234 and DEF-345…
-
https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens covers everything you need, including adding new fields, putting them on screens and making them mandatory. However, Jira does NOT support mandatory fields in the way you are probably assuming. If you want a field to be optional for part of the…
-
Er, both of those links work fine for me, and the doc on creating a notification scheme is correct. Could you tell us what errors you are seeing when you try to go to that page?
-
That's not the assign issue action, that's in the workflow, in a transtion labelled "assign issue" You've got a broken validator on the transition. Probably someone removed a plugin that provided the validator. You should read your log to find oout what the validator was, then you can put it back, and re-edit the workflow…
-
I'm afraid we need more information if we are to help you. Where does this happen, and when?
-
Ok, now that is a bit odd because there are no validators on "assign issue". That makes me suspect that you might be doing assign in the workflow, or that it's something else, so can you do some quick extra tests for us? * Try the inline assignee function - in issue view, click on the assignee and change it to someone…
-
Create a new "field configuration scheme" for the projects that don't want unassigned issues, and set the assignee as a mandatory field in there.
-
The email handlers in OnDemand are the ones that Jira provides off-the-shelf. They don't do much parsing of the data. You could set up components leads, but the email won't set a component.
-
That's correct. The whole point of the resolution field is recording the resolution. If an issue has a resolution, then it is resolved and should be struck out. So, "none" or "unresolved" on the screen mean "there is a null in the database". As soon as you put anything in it, the issue is resolved. Doesn't matter if the…
-
When you say the post-function has marked it as "not resolved", do you mean you have added a resolution of "not resolved"? If so, that's the problem. Your post function needs to *clear* the resolution and you need to delete the resolution of "not resolved" from Jira's list of resolutions. Because ANY resolution means…
-
Anyone who can log in counts as a user. They can log in if they have "use Jira" or "Admin Jira". You can set up anonymous access, but this is really not a good idea for anything other than "browse", because it lets people do things without you being able to log who. That's a spectacularly bad idea in any issue tracker, and…
-
Pretty much answered by the answers to questions you've already asked - see https://answers.atlassian.com/questions/37041901 as an example. To save you re-reading though, no. JIRA is an issue tracker, not a test case manager. There are addons that can do it, and integrations for test-case managers, and you should have a…
-
It's not Atlassian doing it. Most addons are expected to have an impact on, or be used by all users, so the default is a really easy 1:1 mapping. Some addons do implement "licence for a sub-set of users". Not many, and the code is all inside the addons.