Comments
-
I am not sure what you mean by main panel. However, every project has Browse permissions. Set these to align with your requirements and your goal will be realized.
-
Disclaimer: I’m not where I can try this. It would seem to me that you don’t need automation here. Rather set a Condition in the workflow on the transition from Review to In Progress requiring the OE to have a value. Or if the OE is typically filled in at that stage then use Validation and a screen to ensure the user adds…
-
No you cannot do this. To be a “Watcher” for any project they must have a paid license. JSD Customers are non-paid and do not have application access. Customers can only a “Request Participant” for the JSD project(s) they are customers of.
-
I am guessing you are using Portfolio as themes and initiatives are not part of Jira Software. I do not use Portfolio but found the article. jira-portfolio-fundamentals
-
Indeed scrum can and often does apply to non-development activity. If you PM tasks are closely tied to a given development task then including them would make sense. Generally for me, the PM activity happens at the front end and I like to keep things separate. For example, I would have a board for the PM where any…
-
can you confirm that the Done issues are truly done? Is the resolution set for all issues? Is this Kanban or Scrum? Can you share your filter (and sub-filter if Kanban) here?
-
Hi Tom! They do not need admin rights at all. You should check the notification scheme for the project in question. project > project settings > notifications. In there you can define which roles/groups will receive notifications for which events (create, comments, etc.)
-
for cloud the only pre-requisite for installing is that you can navigate a browser and click a few buttons. As for cost and effort estimation to implement a project: * cost - is not project dependent but rather user dependent. You pay per user. Here is the pricing info - jira-pricing. Addons will increase the cost if used.…
-
You will need an addon. Suggestions: Scriptrunner or jql-search-extensions-for-jira-reports
-
Updatedby ... AND updateddate ...
-
Have the admin add your agent to the Create event under project > project settings > Notifications. Generally you will do this by adding the role that the agents are defined in, e.g. Service Desk Team. Check the Rolex they are in for your instance under People.
-
check the notification scheme for the event in question. project > project settings > notifications. Check what roles receive the notification and ensure the user exists in one of those roles.
-
I suspect you have a Business project and as such if you created a Kanban board it is likely to have a Location under your profile. What you can do is add the board to the sidebar but when you click on it it will take you out of the project still.
-
Customers can be approvers today w/o having to be assigned the issue. Customers cannot be assigned issues but you can make them an agent if you want to for some reason. of course this means they will be added to your billing.
-
you can consider creating two boards...and borrowing terms from Wade... Board 1: 'What we are working on now' Board 2: 'Deep Freeze' For this I would use Labels and apply the labels according to the boards, e.g. Board 1 "...labels != DeepFreeze" and Board2 "...labels = DeepFreeze"
-
the easiest way to check who has JSD access and hence which user count against billing is to go to Jira settings > User management and filter of service desk users that are active
-
there isn't an "attendance" button but you could consider hijacking the "Vote" feature for this. It limits a single vote per user. you could also us the Watch feature but that would mean everyone would get a notification anytime the issue was update. yuck
-
Labels are user-definable tags that can be use to help categorize your issues. Sort of like Components but not restricted to a specific defined list. a unique label is created for any text that is entered w/ a 'space' being the label separator. Labels is case sensitive so if I enter Hello hello goodbye test I would create…
-
i don't understand. when i create a NG project it clearly prompts for how 'open' or 'private' you want the project to be.
-
maybe start here - limit-restrict-user's-project-access
-
awesome sleuthing! that now makes sense.
-
maybe i should create the following alert? "*.*" ;-)
-
you cannot configure the default or remove that option. you might check addons that focus on customizing the portal. I have not personally used any.
-
components do not exist as they do in Classic. you could create a field and call it Components but it won't have the same behaviors.
-
that is weird. and if you go back to old view the issue returns? if so i would suggest reporting the issue to Atlassian Support.
-
As Alexey says customers need accounts. However you can consider a login-free portal
-
Hi Marcus! There isn’t an Archive function. What I do is create an Archive project category and I create an Archive Notification scheme which only allows Jira admins to browse the project.
-
well here is what i have determined. I am on cloud and do not see but my coworker does. Which is quite peculiar. It is equally odd that it is showing on an older server version for you. With that said all it appears to do is to handle a situation where the text seems to be taller than the field size. sort of useless IMO…
-
ok so that is interesting indeed. is this server or cloud?
-
not at this point. you might wish to click the "feedback" link and let them know you would like the capability.