Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For users to be able to read the tickets they've created, you just need to add a condition on the ability (see below). You can use the same condition on the <code>:create</code> ability and cancan will pre-fill those attributes for you when it builds a new object for the <code>#new</code> or <code>#create</code> actions.</p> <pre><code># app/models/ticket.rb class Ticket &lt; ActiveRecord::Base # &lt;snip&gt; belongs_to :user belongs_to :employee # &lt;snip&gt; end # app/models/user.rb class User &lt; ActiveRecord::Base has_one :employee end # app/models/ability.rb class Ability # &lt;snip&gt; if user.has_role? :ticket_viewer can :create, Ticket can :read, Ticket, :user_id =&gt; user.id end if user.employee # &amp;&amp; any other necessary conditions can :create, Ticket can :read, Ticket, :employee_id =&gt; user.employee.id end end # app/controllers/tickets_controller.rb controller TicketsController &lt; ApplicationController load_and_authorize_resource def index # @tickets = Ticket.accessible_by(current_ability) # cancan's # load_and_authorize resource will take care of loading ticket(s) for # all controller actions, so I've commented them out @tickets_grid = initialize_grid(@tickets, :include =&gt; [{:user =&gt; :user_type}, :employee_department, :state]) end def show # @ticket = Ticket.find(params[:id]) @reply = @ticket.replies.build # this for comments on ticket @state = State.all # this for a model called State which describe the priority of the ticket (Emergency / High / Normal ) end def new # @ticket = Ticket.new end def create # @ticket = Ticket.new(params[:ticket]) if @ticket.save flash[:notice] = 'Support ticket request created.' redirect_to @ticket else flash[:error] = 'An error occurred please try again!' redirect_to '/dashboard' end end def edit # @ticket = Ticket.find(params[:id]) end def update # @ticket = Ticket.find(params[:id]) if @ticket.update_attributes(params[:ticket]) flash[:notice] = 'Successfuly updated.' redirect_to tickets_path else flash[:error] = 'An error occurred please try again!' render @ticket end end end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCanCan for employees and users
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USgraywh
    1. USgraywh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCanCan for employees and users
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COAnd what about the assigned employee how could he see the assigned tickets only ??? ( employee is a user as well but i don't know if its related to user in the correct way or not) i hope you could help me i have been stuck on this for 3 days
      singulars
      1. PO
      1. USMostafa Hussein
    2. COalso i need to hide the index , for example we made the user can show only what he created , also i need to hide what he has not created form the index
      singulars
      1. PO
      1. USMostafa Hussein
    3. CO@Dexter I've given you an example of how to restrict the read access for a user to tickets he "owns". Only those tickets will appear in the index because they are queried with the condition `"tickets.user_id = #{user.id}"`.
      singulars
      1. PO
      1. USgraywh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload