Comments
-
I cannot think of a single use case, where you would need statuses without transitions. Speaking from a archtitectural POV, an Issues's goal in Jira is to be transitioned into a "final" status. The final status usually has no outgoing transition (apart from possibly "reopen") and sets a Resolution to the issue (if not set…
-
You can just create a custom field using Radio Buttons or Select Lists and have yes / no as the options. Note, that you can translate the Fieldname however you cannot translate the options. If your portal is mainly used in English anyway, that shouldn't be an issue though.
-
Linked Issues are hidden from the Portal by default. So even if your customers have access to the Service Project (which they could get "View-Only" even without Agent License), they will not see Linked Issues in the Portal. So yes, the easiest way for them to know about the specific bug issue is by commenting the Service…
-
I think, that either of you needs to change their Email-Template. In JSM you cannot change the Algorithm of how Jira recognizes replies, you can only switch between replies popping up as new issues or comments. Not sure if ServiceNow matches Emails to Issues if the ID is only in the Email Body, but that would be worth a…
-
Have you performed a Project Re-Index as indicated in this article (in the last step): Archiving a project | Administering Jira applications Data Center and Server 9.12 | Atlassian Documentation ?
-
As far as I know, there isn't really. You can use the "Guest user" feature, but that is mainly meant for whole spaces as well. Are they only viewing content or editing as well? You could try the include-macro, but I'm not sure whether that regards restrictions on the original page.
-
You can use Automation. Trigger would be "Issue created", then you would probably need an if-statement filtering only your Incident requests. Did you actually use "Forms" or the standard request form functionality? Either way, you could configure your request so that the result of the Checkbox (or whatever you used) ends…
-
Nothing gets moved to new Sprints automatically in the background. So once you end a Sprint, are you asked what to do with the incomplete tasks? Options are backlog, Future Sprint or new Sprint. Have they all been moved to the most right column on the board? Otherwise they are not considered "complete". Do they have a…
-
Do the "internal customers" all have Jira Product access?
-
You could work with page restrictions (depending on what level they are allowed or not allowed to see) and use two different user groups for the permissions. When you remove the users from your instance, they then cannot access your Confluence instance anymore anyway. Is it several other external companies needing…
-
So now you can copy the workflow without an error? That's odd. Either way - having a status with no in- or outgoing transition isn't recommended. So even in your productive workflow, you should transition all exisiting issues in that status to a different one (-> for that you need an outgoing transition to at least one…
-
It's not really a "workaround" however it is the correct solution if you want to "reimport" your spaces. A space is - as you found out- moved to the trash before deleted permanently ergo still exists in your Confluence. Hence you cannot create another space with the same key. I am wondering though, what your use case for…
-
Assuming you are the Organisation or Site Admin: Go to admin.atlassian.com , choose your Organisation and select the tab "Billing".
-
So just to make sure we understand you correctly. * You had a project with it's own issue type scheme * You changed the projects issue type scheme to the default scheme * You archived said project * you restored said project And now the project has 0 issues?
-
70 Tickets in one column is quite a lot for a board tbh so that might explain it. Imagine having 70 post its on a retro-inperson-whiteboard and trying to grasp the content of that in one go... The whole point of a board is having a quick overview. Are old tickets cleared "away" automatically or manually? Is it actually one…
-
If you edit the issue you will always have the old info in the history. You could change the description, clone the issue and then delete the old one. That should get rid of all historic changes and data.
-
Do you want an issue raised in your Service Desk, when you are opening a request in their system? In your example, JSM-01. If not, you could put their ServiceNow Email-Adress on a blacklist so it doesn't create issues. Unless they use that Email-Adress to actually open issues as well ;) Or you could use a different E-Mail…
-
Organizations within JSM have nothing to do with the Atlassian Org or SSO. Organizations are merely there to organize your customers (portal-only users and possibly others) and give them access to requests (share with organization). When you configure SSO (you will need Atlassian Access) for that, you can create different…
-
Have a look at this post: https://community.atlassian.com/t5/Team-managed-projects/cbteamsupport/m-p/2002869#M462?utm_source=dm&utm_medium=unpaid-social&utm_campaign=P:online*O:community*I:social_share* Not sure what the reason for your question is, but if you want to report a Scam that's related to Atlassian products you…
-
Can you post a screenshot of the workflow you are trying to copy? I am a bit confused by the background info... In Sandbox, you removed the status from the workflow, then copied it and still had the same error message?
-
How many issues are appearing on your board? One solution might be to limit the number of visible issues to reduce loading times.
-
Check if you've got the gear icon next to your avatar and the Admin UI opens when clicking on it - then you're product admin. However, to give users access to the product you need to be user access admin or Org admin (in the new User Management experience): Give users admin permissions | Atlassian Support
-
You define the name of the swimlane. Can you post a screenshot of the board config tab "Swimlanes"? Generally, issues will appear in the first swimlane, where the JQL matches and only in that one.
-
Have you tried using the Admin UI? -> https://admin.atlassian.com/ I cannot replicate your issue.
-
Is your JSM on a different site than your Jira Software?
-
When setting up a new instance: choose your system language carefully The language used while setting up will determine how your fields, statuses and more are called. If you change the system language later on, that will lead to duplicates of the same status in multiple languages. My suggestion: Go with English as system…
-
Basic but underrated - use as little custom fields as possible Custom fields "litter" your configs and almost all instances have way too many, so * use generic names - then you can reuse the fields for multiple projects * Always question: Do you need the info to be in a specific field (for searches, reports or others) or…
-
I am not that new to Jira anymore. Started out as user in 2016 and quickly became Project Admin and then Admin a couple of years ago. I now consult customers as an Atlassian Partner and help customers with migration, customising and introduction - however, my focus is on the people and how they can benefit from the tool…
-
In the reports it actually doesn't use resolution (I know, it's quite inconsistent to behaviour anywhere else in Jira).